Pricing

What does ongoing help cost after the build?

Care, Growth, and Advisory usually follow a build. They cover the maintenance, new development, and technical leadership the software needs once people are using it.

Discovery and the build have their own scope.

The initial conversation about whether the work is a fit is free.Paid discovery, builds, and improvements are scoped case by case. We agree on the deliverables, timing, and cost before work begins. The monthly figures below cover ongoing work afterward.

Engineering capacity can scale with the work. We agree on the allocation as your needs change.

How we work out what to build

Care

Keep the software your team relies on looked after.

Starting at$3,400 / month
Talk through Care

For a working system that needs maintenance and a clear point of responsibility.

Included work

  • Monitoring and alerting
  • Bug fixes and patching
  • Security updates
  • System documentation kept current
  • Quarterly check-in
  • Direct engineer access
Response and coverage
Priority 1 response
4 business hours
Priority 2 response
1 business day
Coverage
9–6 ET

Growth

Keep improving the software as your business changes.

Starting at$10,100 / month
Talk through Growth

For an ongoing queue of features, reports, and connections.

Included work

  • Everything in Care
  • Engineering capacity starting at half an engineer
  • New features, reports, and connections
  • Monthly planning call
  • Priorities reset monthly
Response and coverage
Priority 1 response
2 business hours
Priority 2 response
4 business hours
Coverage
9–6 ET

Advisory

Get technical leadership and ongoing development from the same team.

Starting at$22,000 / month
Talk through Advisory

For a business that needs help with both the software and the decisions around it.

Included work

  • Everything in Growth
  • Engineering capacity starting at a full engineer
  • Leadership for budget, calendar, and contracts
  • Leadership-table meeting every other week
  • Quarterly onsite visit, with travel included
  • Vendor negotiation
  • Questionnaires and bank and insurer responses
  • 12-month cost and decision calendar
  • Monthly report
  • Priority feature development
Response and coverage
Priority 1 response
1 hour
Priority 2 response
2 business hours
Coverage
8–8 ET

Choosing a package

How do you choose between the packages?

The starting prices give you a first comparison. Which one fits depends on your software, how much work is waiting on it, and who should be responsible for the technical decisions.

What is the practical difference between Care and Growth?

Care keeps a working system looked after, with monitoring, fixes, updates, and current documentation. Growth includes all of that and adds a continuing queue of features, reports, and system connections.

When does Advisory make sense?

Advisory fits when you need someone to lead the technical decisions as well as keep developing the software. It includes help with budgets, calendars, contracts, vendors, questionnaires, and the longer-term decisions around it.

The work gives your team written priorities and decisions, with costs and tradeoffs explained. That helps you decide what to do next and what can wait.

Do these prices include discovery and the initial build?

No. These are starting prices for ongoing work. Paid discovery, builds, and improvements are scoped case by case. We agree on the deliverables, timing, and cost before work begins.Intensive discovery usually comes before a build, so we can understand the business and agree on what the software needs to do.

What if we already have working software?

We can take on an existing system. First we need to understand its condition, how your staff use it, and what we’d be taking responsibility for. That tells us what work has to happen before an ongoing package makes sense. Whether you need a new build is a separate decision.

How we work with existing software

How are support and further changes handled?

Each package lists its included work, response times, and coverage hours. We agree which systems we’re responsible for and how your team reports an issue. New work is discussed and prioritized within the agreed scope and engineering capacity.

Who owns the software and the source code?

Each project agreement defines rights to the delivered work, how reusable components can be used, source-code access, repository and account access, documentation, and third-party licenses. We agree on these terms before work begins.