Arrange a walkthrough

How we work

How we work

Precise scope, honest testing and work you can run without us. The process scales to the job, so a small automation gets a short document, not a binder.

The process

Start small. Each step stands on its own, and you decide whether to take the next one.

  1. No charge

    Process walkthrough

    About an hour, on site or by video. We look at how the work is done today and send you a short written summary with a recommended next step.

  2. Fixed fee

    Feasibility assessment

    For problems worth solving where something is uncertain, such as system access, data quality, calculations or licensing. You get findings, a recommended approach and a fixed-price proposal.

  3. Fixed price

    Fixed-scope build

    A defined improvement, built and tested against acceptance criteria agreed up front, with training, documentation and handover included.

  4. Optional, monthly

    Care plan

    Monitoring, fixes and small changes, sized to what your solution actually needs. Or run it yourselves: it's documented for that.

Prices are agreed in writing for your scope before any work starts. If a solution needs extra software licences, we'll tell you before you commit, and the subscriptions stay in your name.

Illustrative examples

These are typical patterns, not client projects. They show how we'd approach common problems.

Illustrative example

Order intake without the re-typing

A typical pattern, not a client project.

The situation

  • Orders arrive by email, phone and the occasional photo of a handwritten note.
  • One person re-types each order into the main system and a planning spreadsheet.
  • Missing details surface later, when someone has to stop work and chase them.
  • Changes after entry are tracked in that person's head.

What we'd build

  • Orders come in through one simple form or a monitored inbox.
  • Required details are checked on arrival, and gaps are flagged straight away.
  • A draft entry is prepared for a person to review, correct and approve.
  • Approved orders go into the system of record through a supported import.
  • Changed or incomplete orders appear on one shared list.

Illustrative example

Supplier paperwork, read and checked

A typical pattern, not a client project.

The situation

  • Supplier invoices and delivery dockets arrive as PDFs and are keyed into the accounting system by hand.
  • Mismatches with the purchase order are sometimes found only after payment.

What we'd build

  • AI-assisted extraction drafts each entry from the document.
  • Each draft is matched to its purchase order. Anything that doesn't match, or that the extraction isn't confident about, is flagged.
  • Approved entries are posted through the accounting system's supported import.

Illustrative example

Approvals that don't stall

A typical pattern, not a client project.

The situation

  • Purchase requests and job sign-offs are emailed around.
  • Nobody can easily tell what's waiting, on whom, or since when.

What we'd build

  • A simple request form in Microsoft 365.
  • Routing to the right approver based on agreed rules, with reminders.
  • A record of every request and decision.

Illustrative example

The weekly report that builds itself

A typical pattern, not a client project.

The situation

  • Each week someone combines exports from several systems into a spreadsheet by hand.
  • Different people define the same figure in different ways.

What we'd build

  • A dashboard that refreshes from the source systems on a schedule.
  • A written definition for every figure.
  • An exceptions list for late, changed or incomplete work.

Questions people ask

Do you work with Microsoft 365 and Power Platform?

Yes. If you already use Microsoft 365, Power Platform is often the first thing we look at. We check your licences before recommending anything, because not every scenario is covered by a standard subscription.

Who owns what you build?

You own your data and the work built specifically for you. If a solution uses general-purpose components we've built, you get a permanent licence to use and modify them for your business. The agreement spells this out.

Is our data safe with AI?

We only use AI where it genuinely helps, through services you've approved, and we check privacy requirements before any personal information is involved. A person reviews AI output before anyone relies on it.

What size of business do you work with?

Typically owner-managed and mid-sized operations where one or two people carry a lot of the admin load. What matters most is a clear process owner and a problem worth solving, not headcount.

Have a process that's costing your team time?

Arrange a walkthrough