AI Solutions · Workflow Platforms
When the problem is a process, not a question.
Governed AI is the category, and a workflow or agent platform is one of five ways an outcome inside it gets delivered. It is the right one when work moves through steps, handoffs and exceptions — or when a lot of people need safe access to capable tools and you need to see what is happening. There are two routes, and this page says plainly when each one wins.
The boundary
We are Microsoft-centric about your environment and deliberately open about what we put to work inside it.
A platform is one of five ways a business outcome gets delivered with governed AI, and it is the right one only when the problem is a process with steps, handoffs and exceptions, or when people are already working in tools you cannot see. It is not where an engagement starts. An engagement starts with an assessment, because choosing the platform before understanding the problem is how organizations end up paying for capability nobody uses.
All five are governed AI. The option is chosen against the shape of the problem, never against a vendor relationship.
- 01Copilot
- 02Company AI
Accounts - 03Connected
Assistants - 04Workflow
Platforms - 05Tailored
Builds
The category
A governed place where a process can run.
A chat window gives a person an answer and forgets the conversation. A platform keeps the context, the connections and the approved ways of working in one place, so the next person does not start over.
Repeatable tasks configured once. Separate areas per team. Curated reference material. Connections that read from the systems where work already lives and write back into them.
When it is right
When the problem is a process with steps, handoffs and exceptions. Or when a lot of people need safe access to capable tools and you need to see what is happening.
When it is not
When you need one outcome embedded deeply in one system — that is connected assistants. Or when nothing off the shelf matches how you work — that is a tailored build.
The honest part
A platform is only as good as the configuration. Bought and left alone, it becomes another subscription nobody uses. The value is in the tasks somebody sat down and built.
Who sells what
The technology partner sells the platform plus the configuration, then operates it.
A process with steps, a handoff and an exception
Four steps run in order. One is a handoff between teams. One branches off as an exception that needs a person.
A process, drawn
- 01RequestIt arrives
- 02CheckedAnd sometimes it is the exception, which still needs a person
- 03Handed offBetween two teams
- 04DoneWith a record of how it went
The steps are configured once. The exceptions are where the work actually is
A platform is worth having when the shape above is real — steps, a handoff, and an exception somebody has to judge. If the work is one question with one answer, this is the wrong option.
Two routes
Which one wins depends on where the work lives.
Where the work lives decides the route
When the process stays inside Microsoft, Power Platform usually wins. When it reaches past Microsoft, or separate teams each need their own controlled area, AI Workspace fits.
Route one · Power Platform
Inside Microsoft
The process stays in the tenant, on licensing you already hold
Route two · AI Workspace
Past Microsoft
It reaches further, or separate teams each need their own controlled area
Where the work lives decides the route
We name both because every Microsoft-centric reader will ask why they should not use what they already own. The choice is made in the assessment, against the problem.
Route one · Power Platform
Microsoft’s own low-code toolset, inside the tenant you already run.
Automated workflows, small internal apps, reporting and agents, built on the foundation you have already hardened and already pay for.
It is usually the right call when the process stays within Microsoft and the licensing is already held. Starting anywhere else in that situation means paying twice for something you own.
It is the weaker fit when the work reaches past Microsoft, or when separate teams each need their own controlled area with different permissions and different reference material.
Route two · AI Workspace, powered by Goodweek
A governed workspace we configure and your partner operates.
Separate spaces per team, approved tasks configured once, curated reference material, and connections in both directions.
It fits when the work reaches past Microsoft, when separate teams each need their own controlled area, or when you want one place to see every model in use.
It is the weaker fit when everything already lives inside the tenant and Power Platform would do the same job on licensing you hold.
We name both because every Microsoft-centric reader will ask why they should not use what they already own — and that is a fair question with a real answer. The choice is made during the assessment, against the problem.
AI Workspace in detail
A workspace, not another assistant.
Spaces inside one governed boundary
A separate area per team or function, each with its own permissions, reference material and approved tasks, all inside one governed boundary.
One governed boundary
A separate area per team
Its own permissions, its own reference material, its own approved tasks
What each one holds
- Actions, configured once
- Curated reference material
- Connections, both directions
- The governance view
Private or shared, and the boundaries are yours to set
Someone clicks the task rather than writing a prompt, which is what makes this usable by people who will never learn to write one.
- Spaces
- A separate area per team or function — sales, operations, finance, whatever the shape of the business is. Each one has its own permissions, its own reference material, and its own set of approved tasks. Private or shared, and the boundaries are yours to set.
- Actions
- The repeatable tasks, configured once. Someone clicks the task rather than writing a prompt, which is what makes this usable by people who will never learn to write one. The role, the objective, the constraints and the tone are set in advance by whoever owns the process.
- Reference material
- The documents, policies and records the work should actually draw on — curated, not everything the organization has ever saved.
- Connections, both directions
- It reads from the systems where work already lives and writes back into them: a summary posted to a channel, a ticket created, a recurring report that arrives without anyone asking.
- The governance view
- Which models are available, which data they reach, who has access, and what has been used. This is the part that distinguishes a governed workspace from a browser tab, and it is the part a technology partner operates.
Several models, one place. Different work suits different models, so the workspace routes each task rather than committing the organization to one provider. You choose which models are permitted; people choose nothing.
Who this is for
For the technology partner
This is a service you can sell, not a license you resell.
A license with a margin on it is a comparable product, and a comparable product is priced down every year. What is not comparable is operating a client’s AI capability: the access controls, the usage rules, the adoption work, and the monthly review where new use cases get found and old ones get retired. One of those is a line item. The other is recurring revenue, and only one of them is hard for the provider down the street to quote.
You own the client relationship, the contract, the invoice and the licensing. Meraia supplies the method, the configuration and the capacity you would rather not hire.
For the business
Your people are not waiting for permission.
If several people independently reached for the same tool for the same task, something in that workflow was not working and they fixed it themselves. That is worth knowing twice: once as an exposure to close, and once as demand somebody already proved for you.
Where a technology partner supports you, we work through them. Where one does not, we work with you directly and say so plainly.
No client disintermediation. We do not prospect a partner’s market, and we do not approach a partner’s registered clients for services that partner delivers.
What the partner operates
Four layers. The fourth is the one that recurs.
Four layers, and the one that recurs
Secure access, governance and adoption are built once. Ongoing operations is a service that continues.
Four layers
The first three are a project
Secure access, governance, adoption
The fourth
Ongoing operations is a service
What is being used, what it costs, what should be added or retired, and what measurably improved
The only one of the four still generating revenue in month eighteen
The monthly review is the layer the partner operates. The first three are built once; the fourth is the one that recurs.
Secure access
A governed place to work, with approved models and controlled access. The thing that replaces fifteen personal subscriptions nobody can see.
Governance
What data may be used, which connections are permitted, who may do what, and a record of what happened. Written down, not assumed.
Adoption
Spaces configured, tasks built, people shown how. Capability nobody uses is not capability.
Ongoing operations
The monthly review: what is being used, what it is costing, what should be added, what should be retired, and what measurably improved.
The first three are a project. The fourth is a service — and it is the only one of the four that is still generating revenue in month eighteen.
The honest scope note
AI Workspace runs on Goodweek. It is a platform we configure and govern, not software we wrote.
We say this out loud, and we put the name in the product, because we tell partners not to buy a white-labeled service they never have to understand. That advice would be worth nothing if we hid the same thing on our own page.
What Meraia brings is the assessment that decides whether it fits, the configuration that makes it safe, and the operating rhythm that keeps it worth paying for. What Goodweek brings is the platform underneath. A reader who wants to look it up should be able to.
Where we come in
Advice, then the work, then the handover.
Whichever of the five is chosen, the shape of the engagement is the same: one outcome, a baseline measured before anything is switched on, a named owner, and the result published. What changes is the scope and the price.
- 01
Decide whether it is actually your option
The assessment establishes what you already own and pay for, what your people are already using, and which single outcome is worth doing first — with the baseline taken and the owner named before anything is switched on. If the process stays inside Microsoft and you already hold the licensing, we will say Power Platform rather than sell you a second place to work.
- 02
Do the work
The route is chosen against the problem, then configured: the spaces, the approved tasks, the reference material and the connections. A platform bought and left alone becomes another subscription nobody uses, so the configuration is the work. Measured against the baseline, because an outcome nobody measured did not happen.
- 03
Hand it over
The result is published, and the documentation to run it without us is written during the work rather than promised for later. A provider who becomes indispensable has failed at the job.
If you are a technology partner
You own the client relationship, the contract and the invoice. We are the specialist capacity behind it — the method, the assessment, and the delivery depth you would otherwise have to hire. You decide whether we are named in front of your client, and whether we are in the room at all.
If you are a business
Where a technology partner supports you, we work through them. Where one does not, we work with you directly and say so plainly.
Where to start
Start with the evidence, not the platform.
An assessment establishes what you already own, how identity, devices and permissions are configured today, read-only against your own tenant, what AI is actually in use, and which single outcome is worth doing first. If a platform is the right answer, the assessment will say so — and it will say which of the two routes fits. If it is not, the assessment will say that instead.
Technology partners begin with the MSP Secure AI Practice Assessment. Businesses begin with the Secure AI Operations Assessment, offered through your technology partner where one is in place.