Project Lavos

- Build engagements, 2026.

The system, before the pitch.

A Build is a scoped implementation sprint. Six to eight weeks, fixed fee, fifty-fifty payment. The brief comes in, runs through the toolkit, and goes back out as the working version - tracking, lifecycle, payment, CRM, SEO, GEO, channel infrastructure, configured against your actual buyer pattern. At the end you get a delivery list: every repo, every URL, every credential, every written playbook. You own it. The agency does not.

01◆

Foundation Build

$2,500

6-8 weeks · Playbooks 01 · 03 · 04 · 05 · 07 · 08

The standard configuration. Small business on a hosted platform, B2C or simple B2B.

Included

  • - Tracking stack - GA4, Meta CAPI, Consent Mode v2, conversion events instrumented
  • - Email + lifecycle - three to five sequences written, deployed, tested against a real address
  • - Payment stack - Stripe or platform-native checkout, manual payment paths where the buyer needs them
  • - CRM setup - Notion, Airtable, or HubSpot Free, populated with existing contacts and tagged
  • - SEO + GEO foundation - schema, on-page content, prompt set baselined across the five AI surfaces
  • - Session recording - Hotjar or Clarity, scoped to the conversion surfaces

Not included

  • ×No paid media management. Spend goes to the platforms; spend management is a Retainer conversation.
  • ×No new visual identity or photography commissioning. The Build uses assets that already exist.
02◆

Custom Build

$6,000+

Scoped · Playbooks Scoped

Bespoke scope beyond Foundation. Quoted from the actual work.

Included

  • - A written scope document built from a discovery conversation - every deliverable named before the contract
  • - Pricing derived from the same line items that compose Foundation - no opaque markup
  • - Same 50/50 payment shape, same fixed-fee discipline, same delivery list at the end
  • - Custom integrations where the standard playbooks do not fit - booking software, POS, PMS, custom code

Not included

  • ×No hourly billing. Scope is fixed before sign; change orders are written and re-priced, not absorbed.

- Scoped configurations.

Three patterns, quoted from the work.

These are the three Custom shapes that come up most often. Each is the same line items behind Foundation, reassembled to fit. Pricing is derived from the actual scope, not pre-published - the conversation starts with the Audit, or with a brief and a URL.

01

Foundation + GEO

For buyers researching via AI surfaces before they hit the site. FAQPage schema, prompt tracker, off-page citation map across Reddit, YouTube, industry publications.

02

Foundation + B2B

Venue, hospitality, construction. B2B buyer journey - quote-first inquiry, deposit-and-balance payments, vertical schema where applicable.

03

Foundation + Multi-Channel

E-commerce running on more than one channel. Catalog sync as the spine - Shopify, Amazon, Etsy normalized to one source of truth. Unified inbox.

Not sure which Build is right? Start with an Audit - its go-or-no-go points you to the right configuration.

- Request a Build, 2026.

Send a URL.
Name the shape.

Two sentences on the business and the URL is enough to start. Reply within one business day with a scope-confirming question or two and a written proposal naming the configuration, the fee, and the delivery list.

Direct contact

502.345.0525

Reply within 1 business day · No pitch

- Frequently asked, 2026.

The honest questions.

What's the payment structure?

Fifty-fifty. Half on contract sign, half on delivery. No hourly billing, no retainer pressure inside the Build. The delivery list (repos, URLs, credentials, written playbooks) is named in the contract; payment two releases when that list is handed over.

What if my needs go beyond Foundation?

Then it is a Custom Build. Foundation is one bundle of line items; Custom is the same line items reassembled to fit. Three patterns come out of the Custom conversation more often than the others - GEO emphasis, B2B emphasis, multi-channel commerce. Pricing is derived from the per-playbook scoping math, not picked from a menu - same discipline, sharper fit.

Do you offer post-Build retainers?

Yes, but never quoted inside the Build proposal. The retainer conversation opens four to six weeks after delivery, anchored on results-to-date. The published anchor is the Director tier at $1,250/mo and up; whether that shape fits depends on whether the next layer of work is identifiable. If it is not, the engagement stays closed and the deliverables are yours.

Can I add or remove playbooks?

Yes. Adding or removing a playbook moves the Build into Custom territory - same fee math, written scope, same delivery discipline. Foundation is the common shape; the line items behind it are the actual unit of work.

What happens after the six-to-eight weeks?

The Build ships with a delivery list: every repo, every URL, every credential, every written playbook. You own all of it. If a retainer makes sense, that is a separate conversation. If it does not, the Build is done and the system runs on its own. No leverage held.

How is this different from a typical agency engagement?

Three differences. One: the fee is fixed before sign, not estimated and billed hourly. Two: every deliverable is named in the contract and handed over at the end, including credentials - no ongoing dependency on the agency. Three: the playbooks are written documents you keep, not a service you rent. The Build configures the system; you run it after.