How we work

Clear scope. Working handover.

Good technical work includes the decisions, documentation, and support that make a system usable after launch.

The goal

You should know what is being built, why it matters, what it costs, and who owns it when the work is done.

Inside a project / Take a look

You see the work
before it's done.

A scope you can read, a version you can try, and a handover you can use. Walk through a booking project to see what we mean.

Northstar / project room
Step 1 of 4

Agree the scope

First, decide what a finished job looks like. Here's a booking project, with the boundaries written down.

project-brief.md

A simpler way to book a class.

One website. A booking flow your customers can use on their phones.

Included
  • Class schedule
  • Book and cancel
  • Staff booking view
For a later phase

Memberships
A native mobile app

Done means a customer can book, receive confirmation, and cancel without calling the studio.
Scope ready for review

The process

A few steps, in the right order.

  1. Scope it together

    We review the business problem, users, and existing tools. Together we agree on priorities, deliverables, budget, dependencies, and acceptance criteria.

    You get a clear scope.
  2. Build, then review

    You try working versions. We make decisions together, test the important journeys, and agree on changes before adding them.

    You get working software.
  3. Launch with confidence

    We check permissions and integrations, prepare deployment, and hand over the code, access, and documentation.

    You get a system you own.
  4. Keep it useful

    We agree on maintenance, responsibilities, and how to get help as your business changes.

    You get a support plan.

What to clarify before we start

  • Who owns the code, accounts, and data
  • What is included and what costs extra
  • How progress and changes are reviewed
  • Who handles maintenance and support

Common questions

A few practical answers.

Can you work on a system we already have?

Yes. Tell us what it runs on, what works, and what needs attention. We review the existing setup before recommending fixes, extensions, or a rebuild.

Do we need AI or MCP for every project?

No. A website, API integration, or straightforward automation may be all you need. MCP helps when a compatible AI application needs controlled access to your business tools or data.

Can we start with a smaller project?

Yes. We can scope one website, feature, integration, or technical issue first. The next step depends on your priorities, budget, and what we learn.

What happens after launch?

We agree on handover and ongoing support before delivery. Maintenance, response times, hosting costs, and responsibility for third-party services belong in that agreement.

Have a project in mind?

Tell us what you need

VoloTech assistant

AI chat · Coming soon

Hi there. What would you like to build, connect, or fix?

AI replies aren't connected yet. Explore our services or send the team an enquiry.

Draft only. Messages are not sent.