AI automation

The busywork, built out of your week.

Five automations — documents, support, leads, integration and internal knowledge — engineered into the tools you already run, with a person kept in the loop wherever the system is not sure.

Typical build 3–10 weeksFixed price before we buildNo rip-and-replace of your systems

01 How they are built

Five jobs. One engineering spine.

Every automation we build follows the same five steps. That is deliberate: it makes each one predictable to run, easy to combine, and honest about uncertainty.

  1. IntakeWhatever channel the work arrives on — inbox, form, scanner, API.
  2. UnderstandClassify it, read the fields, detect intent and urgency.
  3. ValidateConfidence scores, cross-checks and your business rules.
  4. ActPost, route, assign, reply or sync — in your systems.
  5. Human reviewAnything uncertain waits for a person. Nothing is written silently.

02 The five

Pick one to see how it runs.

Each shows the job it takes over, the workflow it runs, and what it looks like in use.

4–8 weeksDocument automation

DocTrace — invoices, forms, delivery notes

You know this onePaperwork reaches you five different ways, and somebody retypes the same fields into whichever system needs them. A mistyped digit surfaces at month-end.

What changesDocuments are read, checked and filed automatically. The only ones a person opens are the ones the system flagged.

  1. Document arrivesEmail, scanner, upload or phone photo
  2. AI extractionType detected, the right fields read
  3. ValidationConfidence per field, totals cross-checked
  4. Business rulesYour thresholds and approvals
  5. RoutingTo the owning system — or a reviewer
  6. System updatedAccounting, ERP, HR, inventory

How DocTrace works

DocTrace INV-2291
PDFINV-2291 · Northline TradersEmail attachment · accounts@Invoice
VendorNorthline Traders
Invoice no.INV-2291
Net · Tax64,200 · 8,346
Tax ID handwritten · 64%Sent to review
Accounting — bill created✓ posted
Illustrative interface · example data
4–10 weeksSupport triage

SupportRoute — email, forms, tickets

You know this oneEvery channel lands in one pile. Agents read everything to find the urgent message, and simple questions wait behind complex ones.

What changesEach message is read for intent and urgency the moment it lands, routed to the right person, and arrives with a drafted reply to approve.

  1. Customer messageEmail, web forms, helpdesk
  2. Intent detectionWhat the person actually wants
  3. ClassificationBilling, delivery, technical, sales…
  4. PriorityUrgency and customer value
  5. Knowledge retrievalYour policies and past answers
  6. Reply or escalateDrafted answer, or straight to a person

How SupportRoute works

SupportRoute Incoming · Email
Hi, I was charged twice for order #5530. Can you refund one of them?Email · 23:14
Intent: refundQueue: BillingPriority: high
Sorry about that — I can see two charges on #5530. The duplicate is flagged for refund and you’ll get confirmation within one business day.Drafted from Refund policy §3 · awaiting approval
Billing queue — agent notified00:02 after arrival
Illustrative interface · example data
3–8 weeksLead routing

ProspectRoute — every enquiry to the right owner

You know this oneEnquiries arrive through the website, email and the phone. Some sit in a shared inbox over the weekend, and nobody knows which good ones went cold.

What changesEvery enquiry is captured, scored against your ideal customer and assigned within minutes — with a clock on it, so nothing waits unnoticed.

  1. Lead arrivesForm, email, call notes
  2. QualificationCompany, need, size, budget
  3. ScoringAgainst your ideal customer profile
  4. RoutingTerritory, product, availability
  5. CRMContact and deal created
  6. SalespersonNotified with context and a deadline
  7. Follow-upEscalates if the clock runs out

How ProspectRoute works

ProspectRoute New enquiry · 09:42
WEBOperations manager, Kestrel Freight“Need to automate delivery-note processing for 3 depots”Form
82Strong fitLogistics · 40–80 staff · budget stated · named problem
Owner: A. GurungReply due in 2 hCRM deal created
Salesperson notified with context✓ 09:44
Illustrative interface · example data
3–8 weeksSystem integration

UnifyCore — two systems, connected both ways

You know this oneTwo systems that cannot talk to each other, and someone who exports a spreadsheet every Monday to keep them roughly in step.

What changesThey sync in both directions, with retries, a review queue for anything that does not match, and an alert instead of silence.

  1. Multiple systemsStorefront, ERP, accounting, CRM
  2. ConnectAPIs, databases or scheduled exports
  3. NormaliseFormats, units, currencies, names
  4. StructureRecords matched and mapped
  5. UnifyBoth sides kept in step, both ways
  6. IntelligenceClean data ready to report and ask

How UnifyCore works

UnifyCore Storefront ↔ Accounting
StorefrontOrder #5531
AccountingInvoice draft
  1. order.created → mapped
  2. customer matched · existing record
  3. invoice created in accounting
  4. SKU BX-12 unknown → review queue
  5. retry scheduled · alert sent
Illustrative interface · example data
4–8 weeksInternal knowledge

KnowledgeAssist — answers from your own documents

You know this onePolicies live in PDFs, shared drives and a few senior people’s heads. Everyone asks the same colleague, and the answer depends on who you ask.

What changesStaff ask in plain language and get the answer — with the exact section it came from, and only from documents they are allowed to see.

  1. Your knowledgeDocuments, SOPs, policies, past tickets
  2. Permission checkOnly what this person may see
  3. Secure retrievalThe passages that actually apply
  4. AI reasoningAn answer drafted from those passages only
  5. Answer + sourcesCited section and a confidence level

How KnowledgeAssist works

KnowledgeAssist Ask your handbook
Can a site supervisor approve overtime above 10 hours a week?
No. Above 10 hours in a week needs the operations manager’s approval. Supervisors can approve up to 10 hours.
SOURCE HR Policy v4 · §6.2 Overtime approval
SOURCE Operations SOP-14 · Approvals matrix
High confidence2 documents · your access level
Illustrative interface · example data

03 Side by side

Compare the five.

Timelines are typical ranges from signed scope to running in your systems. Your written scope states the exact figure before you commit.

AutomationTakes overLands inTypical build
DocTraceReading and retyping invoices, forms and delivery notesAccounting, ERP, HR, inventory4–8 weeks
SupportRouteSorting, answering and escalating support messagesHelpdesk, CRM, on-call rota4–10 weeks
ProspectRouteCapturing, scoring and assigning enquiriesCRM, sales tasks, email3–8 weeks
UnifyCoreMoving data between systems by export and pasteBoth systems, in both directions3–8 weeks
KnowledgeAssistAnswering the same policy questions every weekChat, intranet, helpdesk4–8 weeks

Connects to tools like these. Anything else with an API or export is confirmed during assessment

  • Excel & Google Sheets
  • HubSpot
  • Salesforce
  • Zoho
  • Odoo
  • Tally
  • SAP
  • QuickBooks
  • Xero
  • MySQL
  • PostgreSQL
  • SQL Server
  • Zendesk
  • Freshdesk

04 Questions

Questions teams ask about automation.

Do we need the SolmiriX platform to use these?

No. Each automation is engineered around your own tools. Some UnifyCore work connects your systems into SolmiriX, our AI analytics platform; most automations connect your tools directly, with no platform involved.

Can we start with just one?

Yes. Each of the five stands alone. You can start with the one workflow that hurts most, and add a second once the first is running.

How are price and timeline set?

After a free discovery call you receive a written scope with a fixed price and timeline. As a guide: DocTrace and KnowledgeAssist usually take 4–8 weeks, ProspectRoute and UnifyCore 3–8 weeks, SupportRoute 4–10 weeks.

Are these built for one industry?

No. They are built around operational patterns — documents piling up, inboxes flooding, leads going cold, systems that do not talk, the same questions asked every week — and tuned on your own records during the build.

What happens when the system is not sure?

It stops and asks a person. Every automation has confidence thresholds and a review queue you control; nothing uncertain is written into your systems silently.

Tell us which job you want off your team’s plate.

In 30–45 minutes we will tell you whether it is worth automating, which of the five fits, and roughly what it would take.