PRICING

Scoped, not listed.

Shipside doesn't publish a price list. The right scope — and the right cost — depends on what runs the business and where the leverage is. Two shops with the same trade often need different builds. A public price list pretends that's not true. We don't.

↩ Prefer to text? (350) 221-0298
01 / WHY SCOPED

Why scope after the fit call.

A website is the foundation. A capture system is a different scope. Owner Inbox and Owner Summary are another layer. Full CRM setup, integrations, and custom internal systems are scoped separately.

Some businesses need one layer. Some need a few wired together. Some need none of it yet — and we’ll say so on the call.

Shipside scopes engagement-by-engagement so the proposal reflects the actual systems being built — not a templated bundle that under-delivers for one shop and over-delivers for another.

02 / HOW SCOPING WORKS

Three steps from "interested" to "written scope."

Step 01

Fit call · 15 minutes

Direct call with Ryan. We ask what the business does, where leads come from, where time gets lost, what is already in place. Honest call on whether Shipside fits — no commitment asked of you.

Step 02

Systems map

If there's a fit, we sketch what runs the business today, where it bottlenecks, and which service groups would actually move the needle. AI Workflow Review where it applies. Output: a written sequence with the work named.

Step 03

Written scope & cost

A written scope and cost — what gets built, in what order, what you'll own when it's done, what ongoing care looks like. You see all of it before any deposit. If the scope changes mid-build, that conversation happens in writing, not in invoices.

03 / WHAT TO EXPECT

What scope conversations sound like.

A scope is built around the layers that actually fit: Website Foundation, Lead Capture, Missed-Call Follow-Up, Owner Visibility, Calendar and Booking, AI Consulting and Workflow Mapping, or Custom Systems. Most engagements use two or three. A few use one. A few use most of them.

Cost depends on which layers, how custom the build, and how integrated the workflow needs to be. We say so on the call — with rough ranges — before anyone signs anything.

If the work isn't worth the scope, we say that too. Sometimes the right answer is "use the system you already have, fix this one thing." That's a five-minute call, not a proposal.

04 / START HERE

The fit call is where scope conversations start.

Fifteen minutes. Honest call either way. Written scope before any commitment.