CarpaTech
Client Portal
AI, automation and data
AI Readiness Assessment
Use-case workshops. Data and process maturity audit. Risk and ROI scoring. A 90-day roadmap.
Custom Copilots and assistants built on your own documents. Document and email automation. Azure OpenAI inside your tenant, with guardrails and evaluations so you can tell when it drifts.
A demo is not a deployment.
Anything can be made to work once, in front of an audience, on a question somebody chose. Production is the other questions: the ones with a typo, the ones about a document nobody should see, the ones where the right answer is that there is no answer. Guardrails, evaluations and a tenant boundary are what separate a pilot from something people use on a Tuesday.
What we build, and what we build around it.
The assistant is the visible part. The rest is what stops it from becoming a liability three months in.
- Azure OpenAI deployed inside your own tenant, in the region you need
- Assistants grounded in your documents, with permissions carried through
- Document and email automation for the high-volume, low-judgement work
- Guardrails on what it will answer, and on what it will refuse
- Evaluation sets, so a change can be measured rather than guessed at
- Logging and review, so you can see what was asked and what came back
- Human sign-off built into anything that leaves the building
- Handover and training, so your team can run it day to day
How a build reaches production.
We scope one thing
A single use case with a measurable outcome. Two at once is how both arrive late and neither gets adopted.
We build and evaluate
Against a real evaluation set, with the awkward questions included. The score before and after a change is visible.
We hand it over
Inside your tenant, documented, logged and with somebody named as the owner. Then the next use case.
Built as a project. Kept alive by the plan.
The build is a project, scoped from a use case and quoted before it starts. What a plan covers afterwards is the part people forget: the Azure tenant it runs in, the identity and access around it, and the monitoring. Premium and CarpaCare carry the cloud infrastructure work behind it, and CarpaCare includes unlimited project hours for the changes that follow.
Projects, migrations and build work are quoted separately and covered by the same SLA.
The rest of this group.
The other three in this group. None of them works well until the foundations underneath can carry it, which is the order we build in.
Have a pilot that never went live?
That is the usual place people are. Tell us what it does and what stopped it. No audit fee, no obligation.