Questions, answered straight.

The Diagnostic is delivered within 5 business days of our intake call. The Build runs 8 to 12 weeks depending on which systems are in scope, and you get the timeline in writing before anything starts. No open-ended engagements, no "phase two" surprises.

It means when we leave, everything works without us. Every build ships with a complete Field Guide: the architecture, every prompt annotated, runbooks for when something breaks, and training for your team. The systems run in your accounts, on your subscriptions, under your logins. Before we close out, your team runs it without us. That's the test. You're not renting access to our process.

Depends what "it" is. If the Diagnostic doesn't surface anything worth building, you walk away with a clear picture of your sales motion for $2,000. If a system we built isn't performing, the Build includes 30 days of post-launch support and we fix what we shipped. Paid Tend begins after that support period and runs month to month from day one with 30 days written notice. During the first 90 days, we watch the system operate in the real market, establish the reporting rhythm, and make the first agreed improvements. We cannot guarantee outcomes. We can give you clear ownership, visible measures, and a defined way to stop.

Whatever already fits your stack. We have nothing to resell and take no vendor commissions. Most builds involve some mix of your CRM and n8n, Make, or Zapier for the workflows that connect everything. We don't take referral fees from tool vendors, and every tool choice is documented in the Field Guide with the reasoning attached.

No. If your team can send an email and use a CRM, they can run what we build. The whole point of the handoff is that it doesn't take an engineer to own it. When something does need deeper attention, that's what the Tend Retainer is for.

The Diagnostic is $2,000, credited in full toward a Build started within 60 days. Builds are a fixed fee starting at $15,000, quoted up front, and the price you're quoted is the price you pay. Tend is $3,000 per month after the Build's included 30-day post-launch support. It runs month to month from day one with 30 days written notice. During the first 90 days, we watch the system operate in the real market, establish the reporting rhythm, and make the first agreed improvements.

No, and this one's in writing. We don't build bots that pose as people. AI does the research, the timing, and the first draft; a real person from your team reviews it, makes it sound like them, and sends it. We keep a public list of lines we don't cross, so you can hold us to it.

Chris does. BloomBound is a boutique by design: you're not handed to a junior team after the sales call, because there isn't one. Small means the person who scoped your build is the person building it.

It's for small B2B teams, whether you make a product or provide a service, where growth has gotten inconsistent and you're close enough to the deals to feel it. It's not for teams that want a spam cannon, a bot army, or 10,000 sends a week. We turn that work down.

Because building before diagnosing is how you automate the wrong thing faster. The Diagnostic scores all five categories of the Motion Map, the same five the free Scorecard covers, so a build gets scoped from your real numbers instead of a guess. If you continue into a Build within 60 days, the $2,000 Diagnostic fee is credited toward it.

Launch is when the system starts meeting reality. Reply rates drift, markets shift, and copy gets tired. Tend covers monitoring, monthly pipeline review, copy testing, and one agreed improvement each month. New systems are quoted separately. During the first 90 days, we watch the system operate in the real market, establish the reporting rhythm, and make the first agreed improvements. The agreement remains month to month throughout.

An intake call, access to the tools involved (CRM and whatever we're connecting), and a point person who can answer questions as we go. Most clients spend a few hours a week during a build, mostly reviewing and giving feedback. We do the grind; that's the deal.

Two places, both short. Where we draw the line is the list of work we refuse and what we build instead. The Charter is the fuller version: the four questions every recommendation gets weighed against, and why we run the company this way. We'd rather you read them before we ever get on a call.

Often, yes, and we will tell you during the Diagnostic. Systems built on records nobody trusts inherit the mess, and then the automation gets blamed for it. Duplicate accounts, dead contacts, and deal stages your team quietly ignores all get cleaned up before anything is built on top of them. Sometimes a week of cleanup is worth more than a month of automation, and if that is where you are, we would rather say it than sell around it.

Yes, everything around the number. RFQs get read on arrival, the part, quantity, material and due date get pulled out and logged, the sender gets a real acknowledgment the same hour, missing specs get chased automatically, and every open RFQ sits on one list sorted by age. What we will not do is price the job. That takes machine time, material cost, capacity and judgment your estimator has and a model does not. Whoever answers an RFQ first usually wins it, and that is the part we can fix.