Fixed scope · Fixed price · Fixed timeline

Two builds you can price right now.

The rest of the work is scoped per engagement. These two are not. Same architecture, same team, a number and a date up front.

See the two buildsEverything else

The two fixed-price builds

0110 business days

CRM Pipeline Install

$2,500

One pipeline, automatic routing, and a first touch measured in seconds.

What the number covers

  • Intake consolidated: forms, calls, chats, and DMs into one pipeline
  • CRM architecture with stages that match how the business actually closes
  • Routing by service, value, and location
  • Speed-to-lead automation targeting first touch inside 60 seconds
  • Sequenced follow-up that does not depend on anyone remembering
  • One dashboard the owner reads without asking anyone
  • Two weeks of post-launch fixes included

Not included: Ad management, custom software, and new site builds are scoped separately.

Start this build
023 weeks

Site & Storefront Build

$3,500

Fast is a requirement, measured on the deployed build.

What the number covers

  • Up to 6 pages, or a storefront with up to 25 products
  • Next.js or Shopify, chosen to fit how the business actually operates
  • Core Web Vitals gate: LCP under 1.5s, CLS under 0.05, INP passing, measured on the deployed build
  • Conversion-built forms wired into the CRM, not into an inbox
  • Analytics and server-side tracking configured at launch
  • Two weeks of post-launch fixes included

Not included: Copywriting, photography, and ongoing content are scoped separately.

Start this build
Fixed scope · fixed price · fixed timelineAnything outside the scope is quoted as its own number

How it runs

Four steps, and a date at the end of them.

The same sequence as any Strygon engagement, compressed. A build this bounded does not need a full audit before it can be priced.

0130 minutes

Scope call

What exists now, what it has to do, and whether one of these two builds is actually the right thing to buy.

02Before anything is built

Written scope + 50% deposit

The scope is written down and agreed. Half the price starts the work, and the clock starts when it clears.

03Against the scope

Build

Built to what was written. Anything outside it gets quoted as its own number rather than absorbed quietly.

04Balance due at launch

Launch + 2 weeks of fixes

It goes live, and anything that surfaces in the next two weeks is fixed without a second invoice.

Business days from the deposit clearingBalance due at launch

Terms of the engagement

What the number is bound to.

Deposit50%To start, balance at launchHalf up front, half when it goes live. There is no third invoice between them.
OwnershipClientHolds every account from day oneDomain, CRM, hosting, and data are created in the client’s name and survive the engagement ending.
ScopeWrittenBefore anything is builtIt does not change without a new number. That protects the timeline as much as the price.
TimelineDay 0Is the day the deposit clearsCounted in business days from there, not from the first conversation.
Structural terms · checkable against the scope documentNo performance figure is claimed here

Start

Pick one, or describe what’s broken.

Name the build in a sentence, or send the situation and Strygon comes back with which of the two fits, or whether neither does.

 

Or email hello@strygon.com