Skip to content
How we work

A written plan first. One workflow at a time. A person approves every output.

No platform to buy, no lock-in, no surprises. Here is the whole process, from the first call to the day your team runs it without us.

From first call to handover
  1. Intro callStart
  2. AI AuditStep
  3. BuildStep
  4. Approval queueApproval
  5. HandoverResult
  6. Run, optionalStep

Four principles we do not bend

  1. Human approval on every workflow.

    Nothing is sent to a client, HMRC, an insurer or a regulator by software alone. Every build has a named approver and a queue.

  2. Inside your tools, not instead of them.

    Xero, QuickBooks, your practice software and your inbox stay where they are. We connect, we do not migrate.

  3. You own everything.

    Workflows run in your accounts, documentation is written for your team, and you can switch us off without losing anything.

  4. Explainable to a compliance officer.

    Each workflow has a one-page record: what data it touches, where it is hosted, who approves what, and how to stop it.

The process, step by step

  1. Intro call

    20 minutes · you and Fatih

    We check fit. If automation is not the right answer for your firm, we say so on the call.

  2. AI Audit

    3 working days · you plus whoever runs the admin

    A 60-minute call, a read-only look at your tools, then a written report: ranked list of what to automate, hours saved per month, build cost, approval points and what to leave alone.

  3. Build

    2 to 4 weeks per workflow · your approver and Fatih

    One workflow at a time on n8n or Make, with error handling, logging and the approval step. You see it running on your real data before anything goes live.

  4. Acceptance and handover

    1 week · your team

    We walk your team through the workflow, the documentation and the "what to do if" page. You accept it before it is paid for.

  5. Run

    optional · monthly, cancel any month · a named contact at Teoq

    Monitoring, small changes, a quarterly review of what to automate next.

Two pages of an AI Audit report: a ranked table of six workflows with hours saved, build cost, approval point and priority, then what to leave alone, risks and next steps.
What the AI Audit report looks like (demo data).

What changes for your team

Today

  1. Document arrives by email
  2. Someone saves and renames it
  3. Data typed into the accounting software
  4. Second person checks
  5. Client chased for the missing piece
  6. Filed, eventually
People
3 people
Time
2 to 3 days

With a Teoq workflow

  1. Document arrives by email
  2. Extracted and validated automatically
  3. Your approver checks a queue, 2 minutes
  4. Posted and filed
People
1 approver
Time
10 minutes

Illustrative. The audit report shows the real numbers for your firm.

Data, security and compliance

  • UK or EU hosting

    Workflow servers and data stores stay in the UK or EU.

  • A DPA before any build

    We sign a data processing agreement before touching client data.

  • Least-privilege access

    Each workflow gets only the fields it needs, nothing more.

  • AI providers that do not train on your data

    Business APIs only, with retention settings checked per project.

  • Audit trail

    Every run, approval and change is logged and readable by you.

  • Off switch

    Any workflow can be paused by your team in one click, documented on the handover page.

If your compliance team wants to see any of this in writing before we start, we send it.

What we will not do

  • Send anything to a client or a regulator without a person approving it
  • Replace your accounting or practice software
  • Scrape data or contact your clients on your behalf without consent
  • Quote a build price before the audit, or change it after the report
  • Lock you into a platform, a retainer or our hosting
Questions

What firms ask before they call.

How much of my time does this take?

The audit needs a 60-minute call plus about 30 minutes of follow-up, around 90 minutes of yours in all. A build needs your approver for a 30-minute walkthrough and then a few minutes a day.

Do you need access to live client data?

Not for the audit. For a build, only the fields the workflow uses, under a DPA, inside your own accounts.

What if the workflow makes a mistake?

Every output waits in the approval queue; nothing leaves the firm without a person. Errors are logged and fixed within the acceptance period.

Can our own developer maintain it?

Yes. Documentation and the handover are written for that, and the Run plan is optional.

What tools do you build on?

n8n or Make for workflows, Supabase for data, Claude or OpenAI for the AI steps, inside Xero, QuickBooks, Clear Books and common practice tools.

Who do we actually deal with?

Fatih, from the first call to the handover. No account managers.

Want the written plan first?

The AI Audit turns all of this into a ranked list for your firm, in three working days.