Files
esh-pfi-infrastructure/stacks/phasefinal-web/conf/site/services/ai/index.html
T
vh 7bd00ae77a feat(phasefinal-web): expand site to a multi-page cluster
Single page grows to nine: custom app development, systems engineering,
hosting, and AI services each get a detail page, plus engagement,
track-record, contact, and privacy. Cross-linked nav and footer on every
page; brand CSS extended in place (still zero external requests, zero JS).

Motivation: an app-store registration review flagged the single-page site
as minimal content. This version is intended to be reverted after approval.
2026-09-28 09:59:43 -07:00

81 lines
3.4 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>AI Services & Engineering — Phase Final, Inc.</title>
<meta name="description" content="AI services and engineering: retrieval pipelines, model serving, agents, and evaluation — model-backed capability run as production software.">
<link rel="icon" href="/favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="/style.css">
</head>
<body>
<header class="page-header">
<div class="hero-inner">
<a href="/"><img class="wordmark" src="/assets/pfi-wordmark-duotone-dark.svg" alt="Phase Final, Inc." style="text-decoration:none"></a>
<div class="hero-copy">
<p class="lede">Model-backed capability, run as production software.</p>
<p class="sublede">AI systems get built, integrated, and operated here the same way everything else does — with requirements, verification, and an owner — rather than as a demo that quietly rots.</p>
</div>
</div>
</header>
<nav class="site-nav" aria-label="Site">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services/software/">Custom App Development</a></li>
<li><a href="/services/systems-engineering/">Systems Engineering</a></li>
<li><a href="/services/hosting/">Hosting</a></li>
<li><a aria-current="page" href="/services/ai/">AI Services</a></li>
<li><a href="/engagement/">Engagement</a></li>
<li><a href="/track-record/">Track Record</a></li>
<li><a href="/contact/">Contact</a></li>
</ul>
</nav>
<main>
<section id="offer">
<h2><span class="num">01</span>What we do</h2>
<div class="section-body">
<p class="detail-lede">A model call is easy. An AI <em>system</em> — with latency budgets, evaluation suites, fallbacks, cost ceilings, and an upgrade story — is engineering. That part is no different from any other discipline the firm practices.</p>
<ul class="detail-list">
<li>
<h3>Retrieval and context pipelines</h3>
<p>Embedding and reranking services, chunking strategy, and evaluation harnesses, so answer quality is measured rather than sampled by vibes.</p>
</li>
<li>
<h3>Model serving and gateways</h3>
<p>Open-weight serving on owned GPUs, API gateways with per-team budgets and full request logging, and routing policies that survive a provider outage.</p>
</li>
<li>
<h3>Agents and workflow automation</h3>
<p>Model-backed automation wired into real operational systems — tickets, documents, messaging — with typed decisions where a decision is all you need.</p>
</li>
<li>
<h3>Evaluation and calibration</h3>
<p>Task-specific eval suites and threshold calibration against client data, so a model swap is a decision, not an incident.</p>
</li>
</ul>
<p class="related"><a href="/services/hosting/">Hosting →</a> <a href="/services/software/">App development →</a></p>
</div>
</section>
<footer>
<span>Phase Final, Inc.</span>
<nav aria-label="Footer">
<a href="/services/software/">Apps</a>
<a href="/services/systems-engineering/">Systems</a>
<a href="/services/hosting/">Hosting</a>
<a href="/services/ai/">AI</a>
<a href="/engagement/">Engagement</a>
<a href="/track-record/">Track Record</a>
<a href="/contact/">Contact</a>
<a href="/privacy/">Privacy</a>
</nav>
</footer>
</main>
</body>
</html>