Who is the Academy for?

Company teams. A company sends the people who will own, build and check its AI, and they work through the roadmap on their own company's knowledge and work. There is a track for each seat: operators, builders and evaluators.

How long does it take?

Eighteen weeks, in five stops over two halves. Start dates and weekly hours will be shared when registration opens.

What does the team leave with?

One system running on your company's data, with one automation acting on it, graded against a question bank your team agrees before it starts.

Pricing will be shared when registration opens. Register interest and we will tell your team first.

Train your team to build AI that runs on context.

For the people who will own, build and check your company's AI. Your team builds on your own knowledge, and goes live only when it passes your own questions.

The roadmap.

Five stops in two halves, over eighteen weeks. Your team first makes a system know what your company knows, then makes it act on it. Beside each stop, what that looks like.

Examples are illustrative, not client data.

Part 1 of 2

Make it know.

Stop 1 of 5Weeks 1 to 4

Bring it in

Capture: Bring in mail, files and records from where they already live.
Structure: Turn a scan or a thread into fields a machine can reason over.

Bring it inStop 1 of 5

VendorApex Supplies

AmountINR 4,18,500

Purchase orderPO 7719

Due30 September

Stop 2 of 5Weeks 5 to 8

Connect it

Graph: Link every record to the people, orders and decisions it is about.
Retrieve: Fetch only what a question needs, and only what the asker may see.

Connect itStop 2 of 5

“Can we pay invoice 0823?”

Invoice 0823Finance

PO 7719Finance

Goods receipt 3321Finance

Payroll ledgerNot permitted

Stop 3 of 5Weeks 9 to 12

Answer with it

Ground: Build the answer from the records, and cite every one.
Serve: Put it in the chat people already use, and log every action.

Answer with itStop 3 of 5

Three-way matchedJira, just now

Logged at 09:14: approved by finance, with the three sources kept beside the decision.

Stop 4 of 5Weeks 13 to 16

Find it and build it

Find the work: Map where a team's week goes, and pick the work worth automating.
Automate: Build it: what starts it, what it checks, and what it does.

Find it and build itStop 4 of 5

Where the finance team's week goes

Checking invoices against POs14 h a week

Chasing approvals over email9 h a week

Building the monthly MIS6 h a week

Picked: invoice checks. They come every week, and the rules are already written down in the rate card.

invoice_0831.pdf arrivesFinance inbox, from Apex Supplies

7.8% above the agreed price.

Checked against PO 7719 and the Apex rate card, clause 4.

Payment heldIn the finance queue

Note to Apex draftedQuotes clause 4

Waiting for finance: send the note, or pay anyway. Either way it is logged.

Stop 5 of 5Weeks 17 to 18

Keep a person in

Decide and measure: Decide what runs on its own and what waits, then measure every run.

Keep a person inStop 5 of 5

Runs on its ownInvoices at or under the agreed price

Waits for financeAnything above it, with the note drafted

212checked

205paid on their own

7held for finance

Last week, from the run log. Every run keeps its sources.

Three tracks, one roadmap.

Same five stops. What each person builds at each one depends on the seat they will sit in afterwards.

Operators

The people who will own and run it: heads of operations, finance and support.

Builders

Your engineers, who ship the pipelines and the automations that act on them.

Evaluators

The people who keep it honest after go-live: audit, risk and IT.

What you will learn to automate.

Work like this already runs in production on Synq. The second half teaches your team to find it, build it and keep it honest.

Complaint Management System
Multi-Level Approval Workflow
Margin Calculation Engine
Finance MIS Engine
Lease Management System
Battery Fault Ingestion Pipeline

Live systems from our portfolio, shown as examples of the work. They are not course projects.

See all twelve

The capstone is the go-live test.

Your team's system is graded twice: on the questions your team wrote before it started, and on an automation run, a batch of test cases where every hold has to be the right one.

The 20 of 22 is our first deployment's own score, shown as the shape of the test. The run figures are illustrative.

20 of 22

questions answered correctly at go-live.

Your question bank is agreed before the first session. The capstone is passed when your system answers it.

And the automation run.

48
test invoices run through your automation.
43
cleared at the agreed price.
5 of 5
held for a person, and every hold was right.

Common questions.

Who is the Academy for?: Company teams. A company sends the people who will own, build and check its AI, and they work through the roadmap on their own company's knowledge and work. There is a track for each seat: operators, builders and evaluators.
How long does it take?: Eighteen weeks, in five stops over two halves. Start dates and weekly hours will be shared when registration opens.
What does the team leave with?: One system running on your company's data, with one automation acting on it, graded against a question bank your team agrees before it starts.
Who teaches it?: The team that builds Synq.
What does it cost?: Pricing will be shared when registration opens. Register interest and we will tell your team first.

Registration is not open yet.

Leave your details and we will tell your team first, with dates, hours and what it costs.

After the roadmap.

Take it back to your companyRun both halves on your own knowledge and your own work.See what gets builtTwelve systems live in production across three enterprises.