Loading page
We scope work before we price it, so the number you get is one we can stand behind. Here's how engagements are structured and what moves the cost.
Your region: US (USD)Nearest hub: San Francisco / New York (EST/PST)
A short, paid piece of work to find out what should be built before anyone commits to building it.
1–2 weeks
Designing and shipping the dashboard, automation or tool itself, in reviewable stages.
6–12 weeks, typically
For teams who want the people who built it to keep improving it after it ships.
rolling, 30 days' notice
Because the honest answer depends on scope. A single dashboard against clean data and a multi-system automation are different pieces of work. The discovery sprint exists so you get a real number, in writing, before committing to a build.
Mostly three things: how many systems have to be connected, how clean the data in them is, and how much of the workflow needs to change rather than be automated as-is. Integrations with old or undocumented systems are usually the largest single factor.
Then we can skip discovery and scope the build directly. We'll still want to see the systems and data first - that review is short, and it's what makes a fixed scope possible.
You do. Code, documentation and infrastructure are yours, in your repositories and your cloud accounts. Ongoing support is something you can choose, not something you're left needing.