Pricing & engagements
You should know what you’re buying, why it matters, and what happens next. We start with a free conversation, define the work, and agree on the price before implementation begins.
01 / How the work unfolds
Start with the free consultation. We’ll help define the right blueprint scope; implementation and ongoing care are separate decisions.
Free consultation
A 30-minute call to learn the problem and decide whether a systems blueprint makes sense.
Bring the messy version. That’s the useful one.
Define the work
Choose the scope together during the free consultation. Map the current process and design the system before committing to implementation.
Your blueprint fee is credited toward implementation if you hire us within 60 days.
Implement & hand over
Build what the blueprint scoped, then test, document, and launch it with the people who will actually use it.
Scope changes are agreed before additional work begins.
Optional / Keep it dependable
Optional monthly maintenance and support to keep the system dependable as your tools, team, and business change.
Support scope and fees are agreed separately.
02 / What shapes the scope
The right comparison includes the time, errors, and delays you’re already paying for. A useful business case makes both sides visible.
Estimate the opportunity03 / Fair questions
The $1,500 blueprint covers discovery and planning for one workflow. The larger blueprint covers up to three related workflows for about $3,500. We use the free 30-minute consultation to decide which scope makes sense for your business.
For either blueprint option, your blueprint fee is credited toward implementation if you hire us within 60 days. You can also use the blueprint independently; implementation is a separate decision.
Implementation has a fixed project price and typically starts around $3,000. Two similar-looking workflows can need very different work. Source access, data quality, review rules, security, and rollout needs all affect the scope. We define those requirements before agreeing on the project price.
Often the opportunity is to connect and improve what you already use. If a replacement is worth considering, we explain the tradeoff and include it explicitly in the proposed scope.
Depending on the design, a system may require hosting, third-party software, API usage, or support. Your proposal should identify expected recurring costs, who owns each account, and what is included in the engagement.
We agree on a baseline and success measures before implementation. Those can include time saved, fewer corrections, shorter cycle times, or earlier visibility. Labor-value estimates are planning inputs; actual return depends on costs, adoption, and measured results.
Ongoing care is optional and starts around $300 a month. During planning, we agree on the maintenance and support scope, who will own the system, how failures will be handled, and what a practical handoff requires.
One useful conversation
Bring the spreadsheet, the bottleneck, or the thing everyone works around. We’ll help you find a sensible place to start.
Tell Nolan what’s getting stuck