Advise

Technical input for business decisions — architecture, planning, code reviews, training, and second opinions on hard problems.

Typical work includes:

  • Requirements analysis
  • Architecture and code review
  • Technical planning and delivery advice
  • Vendor or implementation review
  • Training and stakeholder workshops

Advisory work is usually scoped around a clear question, decision, or deliverable.

Build

Custom software, internal tools and AI-powered applications — built for your team to own and extend, not handed over as a black box.

Typical work includes:

  • New product and feature development
  • Internal tools and workflow software
  • AI-powered applications
  • API design and integration
  • Data migration and transformation
  • Testing, quality assurance, and technical documentation

Every build starts with a written Feature Brief — our proposed approach, scope, assumptions and cost — so we confirm we're solving the right problem before anyone commits to anything.

Support

Warranty, ongoing maintenance, and a team that stays engaged as your software and the business needs evolve.

Typical work includes:

  • Bug fixes and small improvements
  • Dependency updates and security patches
  • Build, release, and CI/CD pipeline support
  • Environment and configuration support
  • Operational documentation and maintenance planning

Support can be arranged as a recurring service or as agreed work when needed.

Pricing

Every Statement of Work uses one of three pricing models:

ModelYou payBest for
FixedOne agreed price for the workWell-scoped work, predictable cost
Time & MaterialsFor the time used, at a day rateExploratory work
Not-to-ExceedFor the time used, up to a fixed ceilingDefined work where scope may shift

When things change

Software development is a journey of discovery — building always reveals requirements or opportunities that couldn't be anticipated. Change Orders keep the agreed scope clear: either side can raise one, it captures what's shifting (scope, timeline, cost), and both sides sign before any new work starts. Until then, the original Statement of Work stands.

Who owns what

Your code is yours. The code, designs and documentation we create specifically for your business are assigned to you on creation. At delivery you receive the source, build scripts, configuration and supporting materials needed to continue without us.

Our tools stay ours, licensed to you. Reusable tools and libraries we bring to the work remain ours, and you receive a perpetual, royalty-free licence to them within any deliverable you've paid for.

Third-party components keep their licences. We track every third-party component used, confirm it's compatible with how you'll deploy the work, and bring in paid commercial components only at your request.

What we need from you

  • A nominated point of contact — someone we can go to when a decision needs to be made or a change approved.
  • Timely responses to questions — as design choices, edge cases and trade-offs surface, a quick answer keeps the work on track.
  • Access to what we need — the systems, data and introductions required to get started and validate our work.
  • Testing together — your users' experience is the most useful signal we get, and it's how we make sure what's accepted genuinely works for them.