Everything people ask before the call.

Our rate is $200 an hour and it's published, so every estimate on the site is hours multiplied by it. Starter plays run $1,200 to $2,400, Workflow builds $3,200 to $8,000, Orchestration $8,000 to $18,000, and Platform work $20,000 to $40,000. Catalogue items can be bought singly from $1,200; the $2,500 minimum applies to custom work we scope from scratch. You get a written fixed-fee quote after scoping, and it doesn't move mid-build unless you add scope.

Not for the catalogue. Every item there is packaged and fixed-scope, starts at $1,200, and can be bought on its own. Our $2,500 minimum applies to custom engagements we scope from scratch, where the contracting, discovery, and handover overhead is real regardless of how small the build turns out to be. Orchestration and Platform items are the one catalogue exception: those are scoped on a call before any payment.

For fixed-fee projects, a 25% deposit at kickoff reserves a build slot. It's calculated from the low end of the quoted range, fully refundable until development starts, and credited against your invoice when it does. The balance is billed at go-live, or at agreed milestones on longer projects.

Fixed-fee scope locks when you sign, which is the point of fixed fee. New asks get quoted as a change order with their own price and timeline. We don't quietly compress the original scope to absorb them, because that's how a fixed-fee project turns into an hourly one nobody agreed to.

You pre-purchase a monthly bucket of hours and we work the highest-value items on your backlog. They start at 10 hours a month on a six-month engagement, then continue month to month with 30 days' notice. Unused hours roll forward one month and then expire, because true hour banking rewards hoarding rather than shipping.

Yes. Mutual NDAs before any commercial conversation if you'd rather start there, and DPAs where the work touches customer data. We don't sign one-sided agreements that bind us indefinitely, and we'll flag anything in your paper that would stop us doing the work properly.

Zach leads technical direction, with consultants responsible for the systems they build. Ross helps define the brief, Lauren coordinates delivery, Devon designs the interfaces, and Jeff manages delivery operations. Your project has named owners and a shared record of scope, decisions, and progress.

n8n by default. It's self-hostable, so execution data can stay inside your own infrastructure, and it's priced per execution rather than per task, which matters at volume. We also build in Make and Zapier when a team already lives there, and natively inside Salesforce or HubSpot when that's the right home for the logic.

Credentials or a sandbox, one person who can answer questions about how the process really works rather than how the handbook says it works, and someone to sign off at the end. Usually a couple of hours a week. The most common cause of a slipped timeline is waiting on access, so sorting that early is the single most useful thing you can do.

Self-hosted n8n inside your own environment, so payloads never transit our infrastructure. Every run writes an audit log, high-risk steps sit behind approval gates, and credentials live in your secrets store. We design against HIPAA, SOC 2, and FINRA control requirements. To be clear about what that is: it's how we build, not a certification we hold, and your auditor still signs off on the result.

Often yes, and it's a common way engagements start. Usually it's an inventory first: what's running, what's silently stopped, what's firing on nothing. Plenty of what we find is fine and should stay. The parts worth rebuilding are the ones with no error handling, no alerting, and no record of what they did.

Yes, and it's often the right shape. We build the first version and set the patterns, your team maintains and extends it. When that's the plan we write for the handover rather than for ourselves, which changes how much gets documented and how clever the code is allowed to be.

Expected, and designed for. Every build includes 30 days of post-launch tuning, which is when the edge cases nobody thought of turn up. After that you can run it in-house from the documentation, or put us on a retainer. Either way the workflows are yours to change.

Every build ships with retries, error handling, and alerting, so a failure pages a human instead of sitting quietly until month-end. The failure mode that actually costs money is the sync that stopped three weeks ago and nobody noticed, which is why jobs report success as well as failure. Response is next business day, with faster windows by agreement.

You do, completely. Source, workflows, platform configuration, and documentation, delivered into your repository and your accounts. You can extend it, change it, or hand it to another vendor without involving us. There's no proprietary framework holding anything hostage.

It depends entirely on what the manual version costs you now, which is why we'd rather you model it than take a number from us. The calculator runs the same math we use in scoping: hours saved multiplied by a fully loaded hourly rate, with a cumulative view over time. Bring the output to the call and we'll pressure-test the assumptions.