How we work

You don’t need to speak software.That’s the point.

You bring the problem and someone who knows how the business runs. We bring the engineer who turns that into a plan you can read, and then into something that works.

Nothing gets built until you have agreed what it is.

The first few days are spent understanding your business, not writing code. You end the week with a plain-English plan and a rough number of hours — and the decision is yours.

  1. Day one, with you

    The engineer sits with you and whoever actually runs the process. Not to talk about software — to watch how the work gets done and where it hurts.

  2. They write it down

    What they think the problem is, what they would build or fix, and what they would leave alone. In plain English, on one page.

  3. A rough number of hours

    Honest, not padded. If the answer is a spreadsheet and an afternoon, that is what the page says.

  4. You say yes or no

    Nothing is built until you agree it is the right thing. If the answer is no, the week cost you the hours it took and nothing else.

Friday note — week 6
DoneBookings land in the calendar without retyping. Tested with Sarah on Thursday.
NextDay-before reminders to customers. Needs the wording from you.
Hours11¼ this week. About four more, then it is finished.

They work. You get a note on Friday.

A few lines in plain English: what got done, what is next, and the hours it took. If something needs a decision from you, it is in that note. Ask for more hours, fewer, or none — there is nothing to renegotiate.

Two short lists, and that is the whole arrangement.

What you give us
  • Someone who knows how the business actually works and can answer a question the same day.
  • A sense of what matters most. Rough is fine — turning it into a list is our job.
  • Ten minutes on a Friday to read the note and say yes, no, or not that.
What comes with the engineer
  • Their own kit, software licences and insurance.
  • Everything set up in accounts in your name — the code, the hosting, the logins. Ours to use, yours to own.
  • A written explanation of how it all works, started on day one and kept current, so the next person can pick it up.
  • Cover arranged by us if they are ill or on holiday.

How the time is counted

Nobody enjoys auditing a software invoice. These are the rules, so you do not have to.

Quarter of an hour at a time

Time is recorded in fifteen-minute blocks and rounded in your favour on the boundary.

What never appears on the bill

Our admin, our internal meetings, the call where we work out what you need, or the handover when we arrange cover for illness or holiday.

One invoice a month

A line per job with the hours against it, matching the Friday notes, so you can see exactly where a quiet week went.

Three promises, in writing.

The things people worry about when they hand a piece of their business to someone technical.

Never a bill you could not have seen coming

You know the rate, you know roughly the hours, and the Friday note tells you where they went. If a job is going to take longer than we said, you hear it before it does — not on the invoice.

Never a system only we understand

It lives in your accounts and it is written up as it is built. If you stop us tomorrow, whoever comes next — us, someone else, a new hire — can pick it up without ringing us.

Never something you did not agree to first

Anything that changes how your business runs is explained in plain English and signed off by you before it is built. We will also tell you when the answer is a spreadsheet, or nothing at all.

The four questions we always get.

Do I need to understand the technical side?

No. You need to know your business; explaining the rest in a way you can decide on is part of what you are paying for.

What happens when the project ends?

Your choice. Keep the engineer on for a few hours a month to look after it, hand it to someone else with the write-up, or ask us to walk away. It keeps working either way.

Do you work on site?

Almost never, and that is deliberate. You are buying hours, not days, and an hour spent travelling or sitting in your office between questions is an hour you pay for that does no work. The work happens remotely; if a morning on site would genuinely save time, we will come.

What if it isn't working out?

Say so and it stops that week. We do not invoice notice, and you keep everything in whatever state it is in, written up.

Ready to put someone on it?

Book a call