← RightHand

For businesses with staff

Your best people are doing work a system should be doing.

Every growing business ends up the same way. A few people hold the process in their heads, everything routes through them, and it works right up until one of them takes a week off. You cannot hire your way out of it either, because every new person has to learn the same undocumented mess.

I build one piece of that into a system you own. Not a platform, not a subscription, not a rebuild of everything you have. One workflow, done properly, and then it is yours.

One workflow, built

$2,500 flat

Two weeks. Not a subscription. No retainer.

What you get

  • +One workflow, built and connected to the tools you already use
  • +The scope written down and agreed before any work starts
  • +Two weeks from the day we agree that scope, not from the day you pay
  • +A walkthrough recording and a written runbook
  • +Two weeks of fixes after delivery at no charge
  • +You own all of it, code and configuration

What it does not cover

  • A second workflow. That is a separate project at a separate price
  • Rebuilding, replatforming, or migrating anything you already run
  • A promised number of hours saved. Anyone quoting one before seeing your process is guessing
  • Someone available during business hours to operate it. Calls are early, evening, or weekend
  • Ongoing operation, unless you want it. That is separate and optional

Either route ends the same way. You describe the workflow, I send back a written scope in plain terms, and nothing gets built until you agree it is right. If it cannot be built the way you want, you get a full refund and I tell you before I start.

How it goes

  1. 1

    Twenty minutes

    Three questions. What does that person do all week, what would you never let a machine touch, and what breaks when they are out. The last one is almost always the workflow worth building.

  2. 2

    The scope, in writing

    I send back exactly what I will build, what it connects to, and what it will not do. You read it and say yes or you correct it. The two weeks start here, not at payment.

  3. 3

    The build

    Two weeks. You hear from me when I need a decision, not for status theatre.

  4. 4

    Handover

    A walkthrough recording, a written runbook, and every credential and file that belongs to you. Two weeks of fixes after that at no charge.

Questions

What counts as one workflow?

One repeated process with a beginning and an end. Catching every enquiry and answering it automatically is one. Sending clients a status update at each stage is one. Pulling data out of documents so nobody retypes it is one. If what you want turns out to be three workflows wearing a trench coat, I will say so before you pay rather than after.

What if it turns out you cannot build it?

I tell you before I start and you get a full refund. I would rather lose the project than build the wrong thing and argue about it for two weeks.

Do I have to talk to you first?

No, but it is usually the faster route. Twenty minutes tells us both whether this is a fit, and it costs nothing. If you already know exactly what you want built, you can buy it and describe it on the form afterwards. The scope still gets agreed in writing before I start either way.

What does it connect to?

Whatever you already run, as long as that software has a way to connect. Most modern tools do. If yours does not, that is a real limit and I will tell you plainly instead of quoting around it.

Are there ongoing costs?

Not from me. The $2,500 is the whole price and nothing renews. Some builds sit on top of software that charges its own monthly fee, and where that is true I tell you which one and roughly what it costs before you agree to the scope, not after.

Who actually does the work?

I do. There is no team, no account manager, and nobody you have never met touching your systems. That is also why it is one workflow at a time and why calls are outside business hours.

What happens to my data?

The scoping form asks for your business details and the process description. It does not ask for passwords or logins and you should never put them there. If a build needs access to one of your systems, you grant it yourself, at the narrowest level that works, and you can revoke it whenever you like.

Not what you are looking for?

If you are a local business that just needs the phone answered and missed calls caught, that is a different thing and it is on the main page. If you are job hunting rather than running a business, that is over here.