Resources ยท Guides

Guides

Longer reads for teams deciding what to automate and how to judge the options.

Woman at an office desk reading and making notes in a notebook beside an open laptop

Read this first

Long reads for the people who have to decide

Written for finance, operations and IT leads choosing what to automate and how to judge the options, including ours.

A guide here is the long, settled version of an argument. The insights are where a position gets tried out; a guide is where it ends up once we would defend it in front of an auditor. Each one takes a single buyer question, works through the mechanics, says where we would draw the line, and finishes with a way to check the answer against your own process.

None of them is a comparison table of vendors. What they do instead is tell you how to run an evaluation that would expose a weak product, ours included: which documents to bring, what to count, which controls to insist on. If a guide makes you want to test something, the research tools are the next step.

Which guide

Start from what you are hearing

Most teams arrive with a complaint rather than a topic. These are the ones we hear most, and the guide that answers each.

Six guides, by the question on your desk

What you are hearingReadThen run
“The bots break every time a supplier changes a screen.”Agentic AI vs RPAAutomation assessment
“Three AP vendors, three demos, all on their own invoices.”AP automation guideFinance assessment
“Will extraction cope with our scanned bills?”IDP evaluation guideDocument test
“The register never agrees with GSTR-2B.”GST automation guideFinance assessment
“The review queue is the new backlog.”Human-in-the-loop guideA demo on your queue
“Where would we even start?”Readiness checklistBook a call
One question each Each guide answers one buyer question and ends with a way to test the answer on your own process.

If two rows sound like your week, read the readiness checklist first. It tells you which of the other five matters more.

In what order

Where each guide sits in an evaluation

A first automation decision usually passes through the same four questions, in this order, before anyone signs anything.

An evaluation, question by question

  1. 01 Is it ready? Readiness checklist: process, documents, data, systems, workflow, AI and governance
  2. 02 Agent or bot? Agentic AI vs RPA: where scripted automation stops on finance work
  3. 03 Which product? AP automation and IDP evaluation: what to test, on whose documents
  4. 04 What stays controlled? Human-in-the-loop and GST: review design, tax checks, the audit trail
  5. 05 Prove it The assessment, the document test, then a demo on your process

Skipping the first question is the most common reason a pilot stalls. The product was fine; the process was not ready for it.

How they are written

What to expect from a PTAS AI guide

One question

Each guide answers one thing

A guide on AP automation is about evaluating AP automation. It does not drift into a product tour, and it says which questions it leaves to another guide.

Your process

Each ends with a test you can run

The finished guides close with a short exercise on your own documents or queue: count the exceptions, pull twenty invoices, draw the approval ladder from policy.

Labelled

Opinions marked as opinions

Where we argue a position, we say so. There are no invented statistics and no customer results; timelines appear only as indicative ranges.

To see how the products are applied, the case studies page explains what a PTAS AI case study will contain and how to ask for a reference conversation. The research and evaluation hub holds the benchmark, both assessments and the document test.

Read it, then score it

Find out which guide applies to you

The assessment scores seven dimensions in about seven minutes and names the two places we would start. Those two usually point straight at one of the guides above.