From First Call to Handover

What happens at each stage of a project, and what you receive from it.

  1. 01

    First call

    A free 30-minute conversation about the process that is costing you time. Bring the person who does the work today, not only the person who manages it, and an example or two of the documents or screens involved.

    What you receive: An honest view of whether it is worth automating, and whether we are the right fit.

  2. 02

    Discovery

    We walk through the workflow step by step with the people who run it, and look at the systems it touches and the cases that do not follow the rules.

    What you receive: A map of the workflow, a list of the systems and data involved, and a recommendation with scope and price.

  3. 03

    Design

    Architecture and screen layouts are agreed before anything is built, including what the system will hold back for a person to review.

    What you receive: A design you can read and approve, so you know what you are getting.

  4. 04

    Build

    Work is delivered in short sprints. Each one ends with a working demonstration on your own data, so you can correct course early.

    What you receive: Working software at every step, not a single reveal at the end.

  5. 05

    Handover and support

    We deploy into your environment, train the people who will use it, and document how it works and how to maintain it.

    What you receive: The solution, its documentation, and support arranged around what you need covered.

Common questions

Who owns the solution when it is finished?

You do. Power Platform solutions run in your Microsoft tenant under your licenses. Custom code lives in your repository and runs in your Azure subscription. We document both so your team or another firm can maintain them.

Do we have to buy licenses through you?

No. We are a Microsoft Cloud Solutions Provider, so we can supply and manage licenses if you want one place for it, but we also work in tenants whose licenses are bought elsewhere.

How do you get access to our systems?

Through accounts you create and control, with only the permissions the work needs. You can remove that access at any time.

What happens when an automation fails?

Items the system cannot process go to a review queue with the reason, and the right person is notified. Failures raise an alert rather than waiting to be noticed, and nothing is silently dropped.

Can you take over something another developer built?

Yes. We start by reviewing what is there, then tell you whether it is worth repairing or rebuilding. We fix what is urgent first and add features in small steps.

How do you use AI in your own work?

AI coding assistants are used with tests written first and independent review before anything ships. The tests and the review, not the assistant, decide what goes live.

How long does a project take?

It depends on scope. A focused workflow is typically delivered in a few short sprints, and we give you a timeline with the recommendation after discovery.

What does support look like after launch?

Support is arranged per client. Some clients keep us on to maintain and extend the solution, and others take it over with the documentation we hand them.

See what we build and recent work.

Start With a Conversation

Free 30-minute call. No sales pitch. We'll talk through your challenges and tell you honestly what we would do.