Book a call

Double the work tomorrow.What breaks first?

We map how your work actually runs, mark where it gets stuck, and build one AI agent for that step, on the systems you already run.

Map your own process. What kind of business is it?

About fifteen questions, results on screen, no email needed. See a whole example

Built for
Manufacturers, distributors, property operators and professional firms.
Working with
Robert Dopart, who runs every engagement himself. About Robert
Running now
A connector between Claude and the ERP at an ISO 9001-certified chemical manufacturer, as a small pilot since September 2026. See what it did
An example: what a made-up coatings plant got back, its drag marked in red. How to read it
  1. CustomerSends an RFQ, a spec, or a repeat order
  2. Raw material suppliersFeedstocks, packaging, contract services
  3. Where the drag isWin the workInbound RFQ through to an order in the systemSales and estimating. Email, Excel, ERP
  4. Worth watchingMake and verifySchedule, procure, run the batch, document itOperations and quality. ERP, MES, LIMS
  5. Ship and billRelease, ship, invoice, collectLogistics and finance. ERP, Carrier portal
  6. CustomerReceives product, certificate of analysis and invoice
  7. Where the drag isManage the accountReorders, account reviews, the renewal or price reviewAccount manager. ERP, Spreadsheet

Click a step marked with a plus to see the work inside it.

How work moves through the plant: a 7-step process. Steps in order: Customer, Raw material suppliers, Win the work, Make and verify, Ship and bill, Customer, Manage the account. 1 rework loop returns work to an earlier step. Marked red, where the drag is: Win the work, Manage the account. Marked amber, worth watching: Make and verify.RFQ orpurchase orderreleased orderraw materialsreleased batchshipment,COA, invoicerepeat customerreorder · reorderCustomerSends an RFQ, a spec, or arepeat orderRaw material suppliersFeedstocks, packaging,contract servicesWin the workInbound RFQ through toan order in the systemSales and estimatingEmail · Excel · ERPMake and verifySchedule, procure, runthe batch, document itOperations and qualityERP · MES · LIMSShip and billRelease, ship, invoice,collectLogistics and financeERP · Carrier portalCustomerReceives product, certificateof analysis and invoiceManage the accountReorders, accountreviews, the renewal or…Account managerERP · Spreadsheet

What you see at the end: your own process, marked where it drags.

The map above is what the questions gave back to a made-up coatings plant. The business and its answers are invented; the map, what stands out and the agent at the top are the site's real output. Here's how it reads.

  • What they expected, and what came up

    They picked “Answering enquiries and drafting replies”.

    Their answers pointed at no visibility of status and recurring reporting instead.

  • Where the drag is

    How would you find out an account had gone quiet?Someone notices, eventually.

    When an account moves elsewhere, do you find out why?We don't. It just goes quiet.

  • What we'd scope first

    Blueprint, not built yet

    Account health and demand signals

    Because they said “Someone notices, eventually.”

See the whole example

Or one for distribution & logistics, hospitality & real estate or professional services.

If the drag is worth fixing, this is how it goes.

Six steps and one decision. Each step is checked against the agreed gate and signed off by you before the next one starts.

Step 1 of 6

Thirty minutes to get to know your business.

A call with Robert about how your business runs and where the work gets stuck. He'll explain a little of what AI can and can't do for a company like yours, and by the end you'll both know whether AIdaea is the right fit.

Where it usually gets stuck

  • Order status, stock, open invoices

    Sales and customer service need them several times a day. The ERP has them, one or two people know how to pull them, so everyone asks those people.

  • Decisions made from memory

    What to buy and what to make this week gets set from experience and a spreadsheet, because pulling the real numbers takes longer than the meeting.

  • Know-how in a few heads

    When the person who knows where everything lives is out, or retires, the questions pile up and the answers slow down.

What you leave the call with

  • Where your process drags, and which system already holds what the people in it keep asking for.
  • Where AI would actually help in your business, and where it wouldn't.
  • Whether it's worth exploring your process together, or a straight answer that we're not the right fit.
Book a call

Step 2 of 6

Find where the work gets stuck, with the people who do it.

We map how work actually moves through your business, with the people who run it, and find where it gets stuck. Then we score two or three opportunities with you, and together we pick the one worth building.

The questions on this site are a first pass at this, before we've met. Map your own process.

Step 3 of 6

Agree what “working” means before anything is built.

We show you ideas, and a demo if it helps you decide. Then we agree the scope that solves the core problem, and write down what “working” will mean: the gate every step of the build is checked against.

Step 4 of 6

One scope, one number, and every question answered.

We walk you through the scope, the acceptance gates and the price, with whoever signs in the room, and answer every question before you decide. Every build is scoped against a payback we agree with you before anything is built.

Step 5 of 6

Built in steps you sign off.

We build it step by step with the people who own the process. Each step is checked against the agreed gate and signed off by you before the next one starts.

Roughly 8–12 weeks for the first build.

Three rules for every build

  1. The gate comes first

    What “working” means is written down and agreed before any building starts.

  2. Nothing moves on without your sign-off

    You check each step against the gate and sign it off before the next one starts.

  3. Not yet means back

    An unmet gate sends the work back, not forward.

Often the first thing we build

A read-only connection between Claude and the system that holds the most-asked answers: usually the ERP, often the CRM next. It runs in your own cloud, under each person's own login, and your team can start asking it questions in the first week of the build.

What happens to your data

  • Runs in your cloud; only answers reach Claude

    We deploy the connector in your own tenant — for a Business Central shop, your Azure. We don't host it, and no copy of your data sits with us. The answers it returns go into the Claude conversation that asked, under the terms of the Claude plan your team uses.

  • Your logins, your permissions

    Each person signs in with their own work account and each system applies that person's own permissions. Nobody sees through the AI what they couldn't already see in the system itself.

  • Read-only to start

    It reads; it cannot write. Writing back to your systems is a separate decision, made later and one action at a time, if you want it at all.

  • Every question is logged

    Each call leaves a line in your own logs: who asked, which tool, whether it worked. Never the data that came back.

On Business Central online already?

Microsoft's own MCP server may be all the connector you need, and we'd rather set that up than build one. It stops short on on-premises systems, custom fields, questions that cross two systems, and rules about who sees what. That's when we build.

When we'd build one

Running at a client as a small pilot since September 2026

A connector between Claude and the ERP

An ISO 9001-certified specialty chemical manufacturer running Microsoft Dynamics 365 Business Central. The client isn't named; that's theirs to give.

  • Within a weekfrom the first working session to go-liveMeasured: Engagement time log, 3–8 September 2026
  • Every callaudit-logged under the asker's own identity, from the first oneMeasured: The client's own log workspace, first production call, 8 September 2026
  • Still upoutside health check passingMeasured: Our external health probe, 20 September 2026
Read the full write-up, including what hasn't been measured yet
See the build loop

Then a decision

The next process, if you want one.

Once the first build is live and has paid for itself, the next process starts back at Explore & Score, with the same gates and the same sign-off. If not, you keep what's built.

Step 6 of 6

What we build is yours.

The system, the data and the documentation are yours, and the people who own the process are trained to run it. There's no lock-in. We stay on to tune it as the process changes.

You'd be working with Robert Dopart.

Robert Dopart

Robert Dopart

Founder

I started as an R&D formulator at a contract manufacturer, then moved into chemical sales. There I saw plants across very different markets, nearly all of them running on spreadsheets, tribal knowledge and data re-keyed from one system to the next. AIdaea builds the tools to fix that, one process at a time.

Read Robert's storyRobert on LinkedIn (opens in a new tab)

Let's talk about your business

Start with the question your team asks most.

You'd be talking to Robert Dopart directly: the person accountable for the build, not a salesperson.

Book a callrobert@aidaea.com

Questions first? Read the FAQ: cost, data, ownership, Microsoft's own connector, and what happens after go-live.