How we work

Five phases, from first call to an automation your team relies on.

You always know what happens next, what you're getting, and what we need from you. Nothing gets built until you've seen the scope and the quote in writing.

The process

What happens, in order

Each phase ends with something concrete in your hands. You can stop after any of them and keep what you've received so far.

  1. Discovery call

    Free

    We talk through how your business runs today: where the hours go, which tasks get repeated, and what you'd fix first if you had the time. We'll tell you plainly whether automation is a good answer, including when it isn't.

    What you get

    • A straight read on whether automation fits your situation
    • A first shortlist of processes worth a closer look
    • Clear next steps, with no obligation to take them

    What we need from you

    • Someone who knows the day-to-day work
    • A rough list of the tools you use
    • The one or two tasks that frustrate your team most
  2. Automation audit

    We map the workflows you want to improve, step by step: who does what, in which tool, how often, and where things stall or get re-typed. Then we rank the opportunities by how much time they give back against how hard they are to build.

    What you get

    • A map of your current workflows, written in plain English
    • A ranked list of automation opportunities
    • Our recommendation on what to build first, and what to leave alone

    What we need from you

    • A walkthrough of each process from the people who do it
    • Example inputs and outputs: real emails, forms, reports
    • View-only access to the relevant tools, where it helps
  3. Solution design

    Fixed quote

    We turn the top opportunities into a written scope: what the automation does, which tools it connects, where a person reviews or approves, and what counts as done. You get a fixed quote for that scope and a timeline we both agree to before any build work starts.

    What you get

    • A scope document you can read without a technical background
    • A fixed quote for the agreed scope
    • A list of the tools and accounts involved, and any running costs they carry

    What we need from you

    • Feedback on the draft scope
    • Decisions on where you want a human to approve
    • Written sign-off before we begin building
  4. Build & test

    We build inside the tools you already use, in your accounts, so nothing lives somewhere you can't see. Every automation is run against real scenarios from your business, including the awkward edge cases. Wherever a wrong answer would be costly, we add a checkpoint so a person approves before anything is sent or changed.

    What you get

    • A working automation running in your own accounts
    • Progress updates as each piece comes together
    • Test results you can review before anything goes live

    What we need from you

    • Access to the tools named in the scope
    • Real examples to test with, good and bad
    • Someone to review outputs and tell us what looks wrong
  5. Launch, training & ongoing optimization

    We switch the automation on with you watching, train the people who will use it, and hand over documentation that explains how it works and what to do if it stops. After launch we keep an eye on how it performs and adjust it as your process changes.

    What you get

    • A live automation your team knows how to use
    • Written documentation and a training session
    • Ongoing tuning, on terms set out in your scope

    What we need from you

    • Time from the team for training
    • One person who owns the automation on your side
    • Feedback from real use, especially when something feels off

A note on timing. How long each phase takes depends on what we're building and how quickly we can get access and feedback. We don't quote a generic turnaround. Your timeline is written into the scope and agreed before the build starts.

Working with us

What you can expect from us

These hold on every project, whatever the size.

Plain-English communication

We explain what we're building and why in words your whole team can follow. If we use a technical term, we say what it means.

You own everything we build

The automations, prompts, and configurations are yours. They're built in your accounts and stay there, whether or not we keep working together.

Security-minded by default

We ask for the least access the job needs, work inside your accounts where we can, and never ask you to send passwords by email. Your data is used for your project and nothing else.

Documentation and training

Every build comes with written documentation and a walkthrough for the people who'll use it, so the knowledge sits with your team and not only with us.

No lock-in

We build on tools you control and document how it all fits together. If you want to take it in-house or hand it to someone else, you can.

People stay in the loop

Automation handles the repetitive steps. Your team keeps the judgment calls, with approval checkpoints wherever a mistake would matter.

Questions

About the process

How long does a project take?

It depends on what we're building and how many tools it touches, so we don't promise a standard turnaround. During solution design we agree a timeline for your specific scope, and it's written down before the build starts.

How do you price the work?

The discovery call is free. Once the solution is designed, you get a fixed quote for a clearly defined scope, so you know the cost before you commit to a build. If the scope needs to change later, we agree the change with you first.

Do we need to switch tools or buy new software?

Usually not. We build in the tools you already use wherever that's practical. If a new tool would make a real difference, we'll say so during solution design, explain why, and list any running costs so you can decide.

How much of our team's time will this take?

Most of your time goes into the audit, when we need people to walk us through their work, and into testing, when we need someone to review outputs. Each phase above lists what we need from you, and one point of contact on your side keeps things moving.

What happens if something breaks or our process changes after launch?

Your documentation covers how the automation works and what to do if it stops. Ongoing optimization is part of the final phase, so we can adjust the build as your process changes. And since everything lives in your accounts, you're never dependent on us to keep it running.

Start with a free discovery call

Tell us where your team's time goes. We'll tell you what's worth automating and what the next step looks like.

Or write to Sebastian@taskrautomations.com