Pricing & Payment

Pricing Table

The price difference tracks real scope, not perceived value: page count, compliance requirements, and local-SEO build-out all increase from Professional through Small Business. See each tier's page for the specific deliverables behind its price.

*Turnaround ranges are a starting-point draft, not yet confirmed as a hard commitment — built from the relative complexity across the three tiers. Treat these as directional until confirmed.

How Payment Works

Every project splits into three even payments:

1. 1/3 due to start — secures your project slot, covers Discovery through Wireframes.
2. 1/3 due after styling is approved — you've seen and signed off on the fully designed (visually complete, content-light) site before the content-heavy final push begins.
3. 1/3 due after final sign-off -- triggers file handover and go-live. Two things happen at once: files hand over to your own GitHub and Cloudflare accounts, and the site goes live.

Ownership transfers with that final payment — clean, and something you can plan around.

Built in Days or Weeks — Not Months

This is a scoped project with a real end date, not an open-ended retainer relationship. Website projects have a reputation for dragging on — and it's usually not the build work itself that does it, it's unbounded feedback and creeping scope. Here's what actually keeps the promise real:

• Scope locks at wireframe approval. The pages and sections are fixed once wireframes are signed off — before Scaffolding begins, and notably before the second payment (which is tied to styling approval). That gap is deliberate: scope is locked well before you're asked to pay again, so you're never approving payment against a moving target.
• One consolidated round of feedback per phase. Feedback is gathered once per phase (Sitemap, Wireframes, Styling, Content) rather than an open, rolling back-and-forth.
• Your response time counts against the timeline, not against us. If a review sits for a week, the quoted turnaround pauses with it — a slow response doesn't read as a broken promise on our end.
• Anything past locked scope becomes a separate, quoted addition — see "Support vs. Complex Work" below — rather than quietly dragging out the original build.

*[NEED FROM PAUL: exact client response-window length — e.g., "3 business days to respond at each milestone before a slot may be rescheduled" — not yet set. Flagged rather than guessed.]

Ongoing Support

Therapist & Small Business tiers: $25/mo — covers ongoing minor updates after launch (see below for exactly what that means).

Professional tier: Professional/About-Me sites don't currently include a retainer option -- ask if you'd like ongoing update support.

Support vs. Complex Work (draft — pending sign-off)

The line below is a proposed default, not yet confirmed — treat it as a draft until reviewed.

Support (covered by the $25/mo retainer): text edits (hours, prices, staff bios), photo swaps, broken-link fixes, minor copy tweaks, adding/removing a single review, small data-file updates (a phone number, a small service-list tweak).

Complex work (billed separately, quoted per request): new pages, new service-area pages, design/redesign work, new integrations (booking systems, forms, analytics), structural navigation changes, anything that touches the data-file schema itself rather than its values.

The simple version: if it's a value in a file, it's support. If it's a new page or a new feature, it's a project.

FAQ

What if my project needs more than what's listed for my tier? That becomes a quoted addition, discussed on the discovery call or flagged during Wireframes — it doesn't quietly expand the original scope or timeline.

Do you offer financing or payment plans? [NEED FROM PAUL: financing/payment-plan terms, if any — not yet decided; per the fabrication rule, contractual/financial terms are never guessed at.]