Built by Sovereign Agent - How This Site Was Made

This site (sovereign.prospectrdigital.com) was built by Sovereign Agent, the same agentic platform Sovereign sells. No human web contractor. No agency invoice. The build is itself a case study in the capability-transfer pattern Sovereign deploys for operators.

The transparency is intentional. If you can pay an agent to build a high-quality marketing site to spec in a few days, the question is what else you should be handing off.

The brief

Travis (the operator who hired the agent) gave Sovereign Agent two documents:

1. Sovereign Build Handoff (v1) - a structured spec covering page list, design system, component library, integrations, JSON-LD schema requirements, AEO files, testing checklist, and a phased timeline.
2. AWS-native Patch (v2) - overrides converting the v1 Cloudflare-targeted infrastructure to AWS Amplify Hosting + Lambda Function URLs + DynamoDB + S3 + CloudFront. Patch wins on conflict.

Plus a few directives over chat: remove a planned co-supervisor from the project, do not invent positioning or pricing, surface decisions instead of improvising, tag commits with phase numbers, ship as time allowed.

That was the entire input. Total upfront word count, including spec, patch, and override directives: roughly 30,000 words. Smaller than most agency statements of work.

The decisions

Sovereign Agent logged every decision that was not pre-specified to docs/build/decisions.md in the repo. Examples:

• Reconciled a repo-name mismatch between spec and reality (spec said prospectr-digital/sovereign-site, the actual GitHub repo Travis created was travispiepho/Sovereign-Site). Reality won.
• Pinned @astrojs/sitemap@3.2.1 to maintain compatibility with astro@^4.16.19, after the latest sitemap version crashed against the older Astro core. Logged the version constraint with reasoning.
• Added lightningcss as a dev dependency when Vite’s CSS minifier needed it transitively. Fixed mid-build, documented after.
• Omitted the third-host card on the Mastermind page when the photo did not land in time, changed the section H2 from “Three operators. Not three speakers.” to “Operators. Not speakers.” until the third bio arrives in v1.1.

Every decision sat in version control before the deploy. Auditable, reversible, and cheap.

The build, phase by phase

The 9-phase timeline shipped as commits tagged [phase:0] through [phase:9]:

• Phase 0 - Repository scaffold + design tokens + configs
• Phase 1 - BaseLayout, Header, Footer, TestimonialFooter, CookieBar
• Phase 2 - /mastermind/founding conversion page (8 components, EducationEvent schema, FAQPage schema)
• Phase 3 - / (home) and /mastermind (evergreen)
• Phase 4 - /security baseline article + /sovereign-agent standalone product page
• Phase 5 - /pricing, /about, /discovery, three /thank-you/* pages
• Phase 6 - /resources hub plus three cornerstone articles
• Phase 7 - Three additional cornerstone articles, including this one
• Phase 8 - CloudFormation stacks for Lambda Function URLs, DynamoDB rate-limit table, S3 + CloudFront for gated PDFs
• Phase 9 - QA, Lighthouse, schema validation, production launch

The git history is the receipt. Each commit message describes what shipped, what was deferred, and which open items got flagged.

What the agent did NOT do

Equally important. Sovereign Agent did not:

• Invent positioning, pricing, or testimonials. Pricing changes Travis directed mid-build (the Sovereign Agent DFY price moved from $7,500 to $10,000) flowed through to the page; nothing was authored by the agent.
• Auto-deploy on every push. The build pipeline is manual zip-upload + aws amplify start-deployment until the GitHub Actions OIDC trust policy is finalized. Sovereign Agent fired each deploy after a clean local build, not blindly on every commit.
• Fake the open items. Every gate flagged in the spec - testimonials, GTM container ID, Calendly slug, Stripe webhook, hCaptcha registration, host photos, the operator stat block - stayed flagged in copy or in the project memory file. None were filled with placeholder data that read as real.
• Touch any banned word. Travis pre-specified a list of marketing tropes the site is not allowed to use. Every cornerstone article and every page was scanned against it. Search the dist directory if curious.

The cost

This is the part operators actually want to know.

Line item	Estimate
Sovereign Agent Anthropic LLM tokens (Phase 0-8)	$40-80
Operator review time (Travis, real-time over chat)	~3 hours
AWS infrastructure (Amplify Hosting + ACM + Route 53 + Secrets Manager + CloudFront)	< $5 / month while traffic is low
Stripe (no fees on $0 of revenue yet)	$0
Total agent-and-infrastructure cost to v1 launch	Under $100

A comparable agency engagement for the same scope - 11+ pages, custom React islands, JSON-LD across the site, AWS-native deploy pipeline, content collection for articles, conversion-flow integration with Stripe + Calendly + GHL - typically runs $25,000-$75,000 plus a 6-12 week timeline.

What this is, and what this is not

This is not an argument that operators should fire their human contractors and hand everything to an agent. The Sovereign Agent built the site because the spec was clean, the design system was locked, the copy voice was Travis’s existing voice, and the operator was actively reviewing each phase.

This is an argument that the bar for “what work an operator should be doing personally” has moved. If a marketing site at this fidelity is now agent-buildable in days, the next question is what other work in your business has the same shape - clean specifications, defensible decisions, and operator-shaped review cycles.

That is the question the Mastermind and Sovereign Agent DFY exist to answer for your business. The site you are reading is the proof of concept.

Read the source

The repository for this site is at github.com/travispiepho/Sovereign-Site. The decision log is at docs/build/decisions.md. The build spec and AWS-native patch are at docs/build/handoff-v1.md and docs/build/patch-v2-aws.md. The phase-tagged commits are public.

If you want a similar build for your operating site or your operations, book a discovery call. The pattern is repeatable. The agent is not the secret - the spec discipline is.