Skip to main content

Run your service business on systems, not paperwork.

We build the automations, live dashboards and websites that take the admin off your office and your crews. It starts with a free 30-minute call.

Book a free callSee the work

Works with what you already use

  • Gmail
  • Google Sheets
  • Google Drive
  • Google Chat
  • Slack
  • HubSpot
  • Supabase
  • n8n

In-house project, field operations

Every van leaves loaded, and the office knows by 8 AM.

A phone checklist and a live office board that replaced a 3-page paper form at the concrete floor coating company where Max runs operations.

Read the case study

The crew home screen: today’s van, its crew, and a morning checklist due by 8:00 AM.
The review step before sending: everything required is filled in, nothing flagged.
of paper per van, per day, replaced
3pages
became items the crew actually counts
38tick boxes
to scope, build and launch it
6days
pilot problems solved, per crew feedback
4/4

What we build

Four kinds of work, all aimed at the same thing: fewer hours on admin, and an office that can see the day.

  • Time-saving automation

    Hand the repetitive admin to a system.

    Instead of: Retyping invoices, chasing confirmations, answering the same questions, copying leads into the CRM.

  • Cost-saving automation

    Spend less on tools, mistakes and wasted trips.

    Instead of: Per-task automation bills, overlapping tools, invoice mistakes found too late, trips back for a missing tool.

  • Custom dashboards

    See the whole day on one screen.

    Instead of: Phone calls to find out where things stand, numbers spread across five tools, reports built by hand.

  • Websites

    A fast website that books the work.

    Instead of: A site that never brings in calls, booking by phone tag, slow pages on a phone.

Tested on a real shop floor first

In-house work at the concrete floor coating company where Max runs operations: real crews, real invoices, real paperwork.

Supplier invoices, read and checked into a sheet

Supplier invoices arrive by email as PDFs. Each one is read, and every line item, plus shipping and tax, becomes a row in the invoice sheet.

Nothing is written unless the rows add up to the invoice total. If they don’t, or the PDF can’t be read, a review email goes to the office instead.

Runs on: Gmail, Claude, Google Sheets

  1. New Invoice Email
  2. Split PDF Attachments
  3. Read PDF Text
  4. Extract Invoice Fields
  5. Totals Reconcile?
  6. Alert: Parsing Failed
  7. Build Sheet Rows
  8. Alert: Totals Mismatch
  9. Append to Invoice Sheet

A monthly inventory report that builds itself

Someone uploads the month’s stock movement report in a simple form. A new tab named for the month appears in the inventory sheet.

AI reads the lines, but plain code does all the adding, so the AI never totals anything. If a line is missing it refuses to write, and re-uploading a month makes a new tab instead of overwriting.

Runs on: n8n form, GPT-5 mini, Google Sheets

  1. Upload the movement report
  2. Extract PDF Text
  3. Parse Line Items (AI)
  4. Build Report
  5. Create Month Tab
  6. New Tab Created?
  7. Tab Exists - Create Dated Tab
  8. Prepare Rows
  9. Write Rows to Tab
  10. Show Result

Example builds

Working examples built to show a pattern. They are examples, not client results.

See every build
  1. Run the demo
  2. Sample email from a prospect
  3. Match it to one approved question
  4. Is it a confident match?
  5. Fetch the studio's approved answer
  6. Leave it in the inbox for the team
  7. Send the approved answer, word for word

Everyday questions answered from approved replies

The AI only picks which approved question an email matches. The reply is sent word for word from a table, so it can never invent an answer.

  1. Run the test set manually
  2. 5 sample support emails (test set) (switched off)
  3. New support email (Gmail)
  4. Normalize the email into one shape
  5. Is the email usable?
  6. Drop repeats inside this batch
  7. Quarantine the unusable email
  8. Already triaged in an earlier run?
  9. New email - not seen before
  10. Classify and draft the ticket (AI)
  11. Skip: already in the queue
  12. Is the AI output in spec?
  13. Manual triage - AI was unavailable
  14. Build the draft ticket
  15. Manual triage - output was off schema
  16. Save the draft as awaiting review
  17. Ask a human to approve the ticket
  18. Approved?
  19. Record: reviewer could not be reached
  20. Mark the ticket approved
  21. Mark the ticket rejected
  22. Create the ticket in your helpdesk (switched off)

Support emails triaged, with a person approving every ticket

Nothing is created until a person clicks approve. Unreadable emails and off-spec AI answers are parked for manual triage, never lost.

  1. New document email (Gmail)
  2. Run the sample documents manually
  3. Is there a PDF attached?
  4. Read the text out of the PDF
  5. Use the email body as the document
  6. 3 sample documents (test set)
  7. Put every document into one shape
  8. Is there enough text to read?
  9. Drop repeats inside this batch
  10. Already imported in an earlier run?
  11. New document, not imported before
  12. Read the fields off the document (AI)
  13. Hold: nothing readable in this document
  14. Skip: already in the table
  15. Do the figures add up?
  16. Build the row
  17. Hold: the figures do not reconcile
  18. Hold: the reader was unavailable
  19. Flag it in Slack for a human
  20. Write it to the operations table
  21. Also write it to your Excel / Google Sheet (switched off)
  22. Also write it to your database (switched off)

Documents read into a table, with the figures checked

Subtotal plus tax must equal the total, and scanned PDFs with no text are stopped before AI can guess at them. Anything that fails is held, not written.

How a project runs

  1. A free 30-minute call

    We walk through where the hours go: the office, the crews, the paperwork in between.

  2. A short written plan

    What to automate first, what to leave alone, and a rough sense of effort. Yours to keep either way.

  3. Build in small pieces

    One workflow or screen at a time, tested on your real data before anyone relies on it.

  4. Hand it over

    It runs on your accounts, with a short guide your team can follow and alerts when something needs a person.

Who you'll talk to

I run operations at a concrete floor coating company. The van checklist, the invoice checks and the inventory report on this site all started as problems with my own crews and my own paperwork.

Max Lavar, Founder, IntelliorAI

More about Max and IntelliorAI

Common questions

Is the call really free?

Yes. It's 30 minutes, there's no pitch at the end, and nothing to sign.

What kind of businesses do you work with?

Service businesses: trades, field service, cleaning, installation and similar teams where the office and the crews still run on forms, phone calls and spreadsheets.

Do I have to change the software I use?

Usually not. We connect the tools you already have, like Gmail, Google Sheets and your CRM, and only suggest a new one when it clearly pays for itself.

What do you build with?

Most automations run on n8n, which can be self-hosted so you pay for a server rather than for every task. Dashboards, apps and websites are custom web builds.

What happens when something goes wrong?

The systems are built to say so. A figure that doesn't add up, a file that can't be read or a step that fails sends an alert to a person instead of carrying on with bad data.

What happens after the call?

You get a short written summary: what to automate first, what to leave alone, and a rough sense of effort. What you do with it is up to you.

Not sure what to automate first?

That's exactly what the call is for. Thirty minutes, free, no pitch.

Book a free call