Two lenses, every choice. Time you get back. Information you have that your competition doesn't. Both of those run through your platform — your data, your accounts, yours to keep.
Kevin — here's what I'm proposing, in one breath.
I build you a working platform on the data you already have, with a few customer-facing surfaces that bring in business and a few internal surfaces that take work off your plate. The whole thing runs on accounts in your name. You're not renting it from me. When the engagement ends, the system is yours and it works without me touching it.
The two lenses below are how I'm thinking about every workstream. Saves time is hours back to your week. Gives advantage is information or visibility that your competitors don't have. Some workstreams do both — but every choice is at least one.
Hours back to your week. Things you do manually now that the system handles automatically — drafted, sent, recorded, reconciled — without you touching it.
Information or visibility your competitors don't have. A website that converts. A bulk-yard quote-request flow that captures demand. A chat assistant that answers your competitive questions in seconds, not days of digging.
Every account in your name from day one — Vercel, Supabase, Anthropic, Twilio. The website and Portal run on hosting you pay for, directly, at provider rates. Your data lives in your database. Sales Assassin runs on your AI account. The backend code lives in a GitHub repository in your name, viewable commit-by-commit as we build. If I disappeared tomorrow, every login still works. That's the load-bearing commitment — and it's structural, not contractual.
What this proposal is. A clear menu of what I'd build, what each piece costs, when it ships, and what stays yours when it's done. The next four tabs walk through the rest:
Trajectory — how this install creates the layer Engagement Two stands on. Menu — the interactive composer where you pick the workstreams. Surfaces — what the website, Portal, and Sales Assassin will actually look like in your green. How It Ships & Stays Yours — the 16-week sequence, the security commitments, and how handoff builds alongside the work, not at the end.
Engagement One builds the foundation. Engagement Two and beyond are the things you'll want once you see what the foundation lets you do — and they're cheaper to add because the foundation is already yours.
Kevin — most platforms try to sell you everything at once. I'm building the install first. The reason matters: once your data is running through your own database, once your customers are flowing through your own website forms, once your Portal is the surface you check in the morning — adding the next thing isn't a project, it's a Tuesday.
Here's the trajectory I see for you. None of this is in scope for Engagement One. It's here so you can see where the install points, not so you commit to it now.
16 weeks. $14K foundation + selectables you compose. The platform goes live. Your website refresh, the Bulk Yard quote-request flow, Sales Assassin V1, QuickBooks integration, the Time Savers. By week 16 you operate the system alone — that's the silence test, and it's load-bearing.
Everything below this point assumes the install is already live and running.
What changes. V1 ships with the substrate I built with you during the install — blower-truck competitor profiles, public bid records, park district contract data, all current as of the build. V2 is when scheduled ingest gets added: the system goes out and pulls fresh data on its own — new park district awards as they're posted, competitor permit filings, public RFP listings, anything in the public-record space worth tracking. You stop asking "is this still current?" because the freshness is the system's job, not yours.
Why it's a separate engagement. V1 is install-and-walk-away — you own it, you run it, no recurring obligation. V2 is a different commercial category: ongoing service that keeps the data alive. Different shape, different conversation. We have it when you've used V1 enough to know what fresh data actually changes for you.
What changes. Phase 1 (in this engagement) takes quote requests and notifies you. You quote, customer responds, you schedule. Phase 2 adds online ordering — the customer picks the volume, picks the delivery window, pays online, and the order lands in your system fully booked. PCI handling, payment processing integration, inventory-aware scheduling.
Why it's a separate engagement. Phase 1 is the proof that the demand is there. If quote requests come in steadily for 90 days, Phase 2 is the obvious next step. If they don't, we don't waste money building a checkout for traffic that isn't there. Phase 1 earns the right to Phase 2.
Crew scheduling. Field operations capture from the truck. Job-cost vs estimate tracking. Customer self-service for delivery status. Things I can't predict — but you'll see them, because the platform makes them visible. Each new surface is a small engagement, not a re-platform, because the foundation already exists.
The trajectory math. Engagement One carries the foundation cost — the database, the hosting, the integrations, the pattern. Every engagement after this one is just a new surface or a new flow on top of that foundation. The install pays itself off twice: once in the time and advantage it gives you over the next 90 days, and once again every time you add the next thing for less than half what it would have cost without the foundation in place.
An interactive menu of what I'd build. Every install starts with the foundation. From there, you pick which workstreams join — each priced standalone so you see exactly what every choice costs.
How this works, Kevin. Engagement One is a pattern, not a fixed package. Every install carries the foundation — what everything else stands on. From there you compose your install: pick the workstreams that matter most for how you actually run.
Every workstream is tagged through your two lenses — saves time or gives advantage — so the cost of each choice is also a choice about what kind of value you want first.
The total at the bottom updates as you select. When you're ready, hit Copy My Selection and text or email what you've picked. Engagement letter lands within 48 hours.
The foundation Engagement One always carries. Required because everything else stands on it.
Five workstreams. Each priced standalone. Click any card to add it to your install — or unselect it. Your total updates live at the bottom.
Five mock-ups in your green. Not final design — directional. Built to show how the surfaces hang together, how the brand carries through, what your customer sees, and what you see when you log in.
Two services. Two customers. One company that owns its trucks, its yard, and its word.
Playground mulch, commercial mulch, erosion materials — placed precisely, faster than by hand. IPEMA-spec wood fiber for park districts.
Request an Estimate →Mulch, topsoil, gravels, stone — delivered to your driveway. Schedule by the cubic yard. Repeat customer? I remember.
Schedule a Delivery →Quote any product. Delivery typically within 3 business days.
Triple-shredded, dyed brown. By the cubic yard.
Premium screened loam. Lawn or garden ready.
Driveway base, drainage, hardscape backfill.
Aged leaf-and-yard-waste compost. Garden-grade.
Hi Sarah —
Your delivery for 4 yd³ of screened topsoil is confirmed for Thursday, May 7th. Estimated delivery window: 10:00 AM – 12:00 PM.
Please make sure the driveway is accessible and the drop spot is marked. If you need to change anything, just reply to this email — it goes straight to dispatch.
Thanks for choosing Lavin.
16 weeks. Eight discipline-named gates. ROI surfaces ship first — your website goes live in week 6, time-savings start the same week. Handoff isn't a moment at the end; it builds alongside the work.
Standard architecture you've already partially paid for. Every account in your name from day one.
The install runs on accounts you own outright. Cloud-owned means every login is in Lavin Companies' name from day one — the website hosting, your database, the AI account, your existing QuickBooks. I have admin access during the engagement so I can build. At handoff, I revoke it. Your billing relationships are direct with each provider.
This is the same setup I run for my own work — proven, deploys in days once we know what your data looks like. Nothing here is custom infrastructure; the build effort is in the substrate (your data) and the surfaces (Portal, Sales Assassin, Time Savers) — not in re-inventing the plumbing.
Website live by week 6. First time-savings live by week 6. Sales Assassin by week 10. Production read week 13–14. Handoff week 15. Silence test week 16.
Each phase ends with a gate — a hold-point where we walk what's built so far and confirm before moving on. Gates aren't progress milestones; they're the discipline that keeps the install operator-built. If a gate fails, we hold and resolve before continuing.
The sequence is built around what gives you ROI fastest. Your website refresh with the bulk yard quote-request flow ships in week 6 — that's a customer-facing surface earning its keep before the engagement is half over. Sales Assassin V1 follows in weeks 9–10. The time savers and QuickBooks integration land mid-engagement so the back-office relief is steady.
Not contract clauses. Actual setup decisions you can verify. Plus what I explicitly don't do.
Operator-built means three things in practice: account ownership at every layer, your data only in your database, walk-away preserved by how it's built, not by promises. The six commitments below name what each of those looks like in practice — what gets set up, what you control, what happens when something goes wrong.
I'm a one-person practice, not an audited platform. So:
No SOC 2 / ISO 27001. I don't carry compliance certifications. The setup follows standard cloud-security practices (encrypted data, secure logins, multi-factor on admin) but I don't produce audit reports. If your buyers ever require certifications, that's a different conversation.
No payment-card or health-data handling. Phase 1 of the bulk yard quote-request flow doesn't take payments — it gathers requests and notifies you. If you want online payments later, Phase 2 brings that with proper PCI handling. Health data isn't in scope.
No 24/7 support. After handoff, you operate the system. I'm available for new engagements, not on-call. If you want ongoing support, we scope it separately.