AI automation

21-Day Build · for service businesses

Only what's missing, working in 21 days.

Connections between your tools, AI for the repetitive work, and dashboards your team trusts. It runs next to the old way until it works.

Working in 21 days from access, or your build fee back. Half paid only when it works. Full terms

The problem

Why automation usually breaks.

  • It's a tangle of no-code steps that only the person who built it can read.

  • It's switched on all at once, so one mistake stops the whole team.

  • Nobody checks the AI, so it gets things wrong in front of customers.

  • Whoever built it moves on, and nobody owns it.

21-Day Build

What we build.

Connections between your tools

The CRM, the spreadsheet, the project tool and the accounting software share the same data, so nobody retypes it.

AI for the repetitive work

Reading emails and forms, sorting requests, drafting replies and updating records, checked by a person until it's accurate.

Dashboards your team trusts

The numbers you currently chase people for, in one place, updated without anyone touching a spreadsheet.

Production code, in your accounts

Where something has to be written, it's production code in your repository. Every account and key is yours.

Timeline

How the 21 days run.

  1. Day 1

    The clock starts the day we have the access we agreed.

  2. Week 1

    Connections between your tools, built and tested on real data.

  3. Week 2

    AI agents and dashboards added, with a person checking the AI's work.

  4. Week 3

    It runs next to the old way. Your team switches over once it's doing the job.

Our promise

Working in 21 days from when we get access, or the build fee back. Half is paid only when it works.

Read the full terms

Fit

Who it's for, and who it isn't.

A good fit

  • US service businesses with 20 to 100 staff
  • Five or more paid tools, and people moving data between them by hand
  • You've paid for software help before

Not a fit

  • Businesses that run everything on one all-in-one industry software
  • AI that decides who gets hired, a loan, housing or insurance
  • Automated texts or calls to consumers

Businesses

AI automation we buildfor service businesses.

Each one starts in tools a service business already pays for and adds only what's missing.

  1. Website formGmailHubSpotSlack
    1. 1Enquiry arrivesFrom the website form or straight into the shared inbox.
    2. 2AI reads itPulls out the company, contact, service asked about and how soon they need it.
    3. 3CRM updatedMatches an existing contact or creates one, and logs the enquiry against it.
    4. 4Owner assignedRouted by service and region, with a Slack message to that person.
    5. 5Reply draftedA first reply waits in Gmail for the owner to edit and send.

    AI automation · Sales inbox

    4Tools connected

    Every enquiry filed, assigned and answered in draft.

    AI reads each enquiry from the form or the shared inbox, files it in the CRM, routes it to the right person and drafts a first reply for them to send.

    How the enquiry-to-CRM automation works
  2. Bank feedQuickBooksClickUpGmail
    1. 1Payment landsPicked up from the bank feed as soon as it clears.
    2. 2Matched to invoicesCompared with open invoices by amount, reference and client name.
    3. 3Clear matches closedMarked paid in QuickBooks, and the ClickUp project shows the client is up to date.
    4. 4Unclear ones queuedPart-payments and odd references go to a review list with the AI's best guess and why.
    5. 5Reminders draftedOverdue invoices get a polite reminder drafted for the accounts team.

    AI automation · Finance

    4Tools connected

    Payments matched to invoices, with only the odd ones left for a person.

    Bank payments are matched to open invoices as they clear. Clear matches close themselves, and the odd ones go to a short review list with the AI's best guess.

    How the payment matching automation works
  3. HubSpotAsanaGoogle DriveQuickBooksSlack
    1. 1Deal marked wonThe trigger is the stage change sales already makes in HubSpot.
    2. 2Project set upAn Asana project from the right template, with the team and dates filled in.
    3. 3Files and accessA client folder in Google Drive, shared with the right people only.
    4. 4Billing readyThe customer and first invoice created in QuickBooks as a draft.
    5. 5Team toldA Slack channel opened with the deal notes, so nobody asks sales again.

    AI automation · Operations

    5Tools set up

    One deal marked won, and five tools are ready for the client.

    When a deal is marked won, the project, the shared folder, the first invoice and the team channel are all set up from the deal record, with nothing retyped.

    How the client onboarding automation works

All service-business case studies

The team

Who you'll work with.

Senior people scope, build and look after every project. The people you meet on the first call are the people who answer when something needs fixing.

Muhammad Furqan Abid, Founder at Invitrex

Muhammad Furqan Abid

Founder

Leads engineering on every build: the scope, the architecture, and how the AI parts behave once real people use them. Six years building software.

Muhammad Zaid Ashfaq, Managing Director at Invitrex

Muhammad Zaid Ashfaq

Managing Director

Runs delivery and care. He keeps each build on its 21 days, and he's the person you talk to when something needs a decision, during the build and after it.

FAQ

21-Day Build, answered plainly.

See every question

The 21 days start on the day we have the access we agreed we need: logins, API keys, repositories and so on. If what we agreed isn't working 21 days after we get access, you get the build fee back. The full conditions are on our guarantee page.

The build fee is split in two. The second half is only paid once the build does what we agreed it would do.

No. The new system runs next to the old way of working until it works. Your team only switches over once it's doing the job.

Anything the AI does for your customers or your money is checked by a person until it's accurate. You see what it gets right and wrong before anyone relies on it.

You do, from day one. We build in accounts you own, the code lives in your repository, and the keys are yours. If we stop working together, nothing has to be moved or bought back.

Working in 21 days from access, or your build fee back. Half paid only when it works. Full terms

Book a free 30-minute call