Example process: from request to approved quote.
This simulated example flow shows possible steps using Dynamics and bexio. It is not a live customer run or live AI system.
Synthetic sample data — not Theia pricing.
Human approval remains part of the example process.
Discuss an example process for your workflowFrontier Firm, Frontier Company — what just happened?
Two terms that are easy to mix up — and the difference between them is exactly the point that matters for you.
The Frontier Firm — the destination.
That's what Microsoft's Work Trend Index calls companies with intelligence on tap, where people and AI agents work as one team. It is a way-of-working framework, not a company-size threshold or certificate. The relevant question is where agents can safely take on defined work while people remain responsible.
The Microsoft Frontier Company — the delivery organisation.
In July 2026, Microsoft announced a dedicated organisation with a 2.5 billion dollar investment and 6,000 specialists, initially working with customers such as Unilever and the London Stock Exchange. Its delivery language is source context, not a promise made by Theia.
Our position: “Frontier Firm” is a Microsoft research framework, not a certification. Theia is not the Microsoft Frontier Company and is not endorsed by it. Our offer starts with one scoped SME workflow, its quality bar and the controls required for production.
Read the full analysisOur commitments for one scoped workflow.
This is Theia's own delivery model — not a Microsoft certification and not a promise made on Microsoft's behalf.
A controlled production slice.
We define one workflow, its acceptance criteria and human decision points. We build and evaluate it against realistic cases, then take it into controlled production after approval — typically within 4–8 weeks.
The required systems, connected.
An agent is only as useful as the systems and permissions it can use safely. We document and connect Microsoft 365, Dynamics and the Power Platform — plus bexio, Abacus or industry software where the scoped workflow requires it.
See the bexio integrationControls before go-live.
For the selected services we review data flows, processing regions, subprocessors, permissions and retention. The agreed controls and human approvals are documented before production — because the answer differs by architecture.
Curious which Microsoft tools sit behind this? See our Microsoft AI stack overview.
What an agent takes off your plate.
No future scenarios — four examples built today with Copilot Studio, Dynamics and the Power Platform.
The quoting agent
Pulls customer data from the CRM, items and prices from bexio, and assembles the draft quote. Your sales team reviews and sends — in minutes, not after hours.
The support agent
Answers recurring customer questions from your own knowledge base, around the clock — and hands over to your team the moment it gets demanding. Cleanly logged in the CRM.
The back-office agent
Reads orders and enquiries from the shared mailbox, records them in your system as structured data and puts the task in front of the right person. No more re-typing.
The briefing agent
Compiles the dossier before every customer meeting: recent orders, open invoices, latest correspondence. Your field staff arrive prepared — without an hour of digging.
A controlled production slice in 4–8 weeks.
The 4–8 week range applies to a custom, clearly scoped workflow. Our productized Microsoft 365 Support Agent follows a standardized scope and a separate activation timeline.
1 · Scope & evaluation plan
Together we define one workflow, baseline, target metric, acceptance cases and the points where a person must review or approve. You then receive a fixed quote for that scope.
2 · Build & validate
We build the production slice, test it with realistic cases and measure it against the agreed quality bar. Human approval remains mandatory at the defined decision points.
3 · Controlled go-live & operation
After the documented go-live decision, we monitor quality and exceptions, improve the workflow and only then discuss a separately scoped expansion.
Microsoft is our core business.
We have delivered Dynamics 365 and Power Platform integrations for years. Copilot Studio extends that stack for clearly scoped agent workflows.
Proven on AppSource.
Our bexio↔Dynamics connector is published on Microsoft AppSource — reviewed by Microsoft, in production at Swiss SMEs.
Fixed quote.
The quote after the intro call is the price. Changes in scope are quoted before we build.
Controls made explicit.
We document data flows, processing regions, subprocessors, access, retention and human controls for the selected architecture before go-live.
Advact AG
Advact demonstrates the integration foundation: Dynamics 365 as the central platform and bexio synchronized automatically, delivered in one month. It is not an AI-agent reference; it shows the data and integration groundwork a workflow can build on.
Frequently asked questions
Which process will you hand over first?
Tell us in 30 minutes where things grind — we'll tell you whether and how an agent takes it over, and you'll get a fixed quote afterwards. No obligation.