Skip to content
Civware

AI that earns its placein your business

Civware plans, builds and runs AI agents, assistants and automations around one measurable job at a time, so you see what each is worth before you invest in the next.

Book a call See how we work
Plan of one job running A request passes through five stages: understand, look up, act, check and record. Between look up and act, the route runs through an approval card, where a person approves the action. Each step is written to a log. FIG. 01 ONE JOB, RUNNING 1 REQUEST · 5 STAGES · 1 APPROVAL 01Understand 02Look up 03Act 04Check 05Record Approval REQUEST ACTION Update the record ApproveEdit WAITING FOR A PERSON APPROVED BY A PERSON LOG 01 understood 02 looked up 03 acted on approval 04 checked
Plan of one job running A request passes through five stages: understand, look up, act, check and record. Between look up and act, the route runs through an approval card, where a person approves the action. Each step is written to a log. FIG. 01ONE JOB, RUNNING 01Understand 02Look up 03Act 04Check 05Record REQUEST APPROVAL Update the record ApproveEdit WAITING FOR A PERSON APPROVED BY A PERSON LOG 01 understood 02 looked up 03 acted on approval 04 checked
Fig. 01 One job running. Nothing changes in your systems until a person approves the action, and every step is written to a log.

Why AI pilots stall before they reach everyday work

  1. 01

    No clear owner or measure

    Nobody owns the result and nobody agreed what success looks like, so there's no way to show the pilot worked, or to decide what comes next.

  2. 02

    No safe way into the systems

    The work needs your CRM, documents or finance system, and there's no approved, limited way for the AI to reach them.

  3. 03

    Output people don't trust

    If people can't see where an answer came from, they check everything by hand, and the pilot quietly stops being used.

What we do

AI services only, from choosing the first use case to running AI in production.

See all services
01

Plan

Decide where AI is worth it, and keep its use accountable.

02

Build

The agents, assistants and automations that do the work.

03

Connect

Link AI to the systems and data the work depends on.

04

Run

Test it, watch it and keep it improving once it's in use.

How we work

Four stages, with a decision point between each, so you never commit to more than the next stage.

How each stage works
  1. 01

    Discover

    Choose one job, and agree how success is measured.

    Decision pointBuild a pilot, or stop here.
  2. 02

    Prove

    A working pilot on real data, tested against your own examples.

    Decision pointGo or no-go, based on the results.
  3. 03

    Launch

    A small group first, with monitoring and human review.

    Decision pointWiden use, adjust, or pause.
  4. 04

    Grow

    Expand when the results support it.

    Decision pointExpand, or start the next job at Discover.

What you can count on

Measured
Every job has an agreed measure before work starts, and you see the result before deciding on the next step.
Tested
Each system is tested against your own examples before launch, and monitored once people use it.
In your control
People approve the actions that matter, each system gets only the access its task needs, and there's a record of what the AI did.
Yours
You keep what we build: the code, prompts, configuration and documentation.
Private
Your data is used only for your project, and it isn't used to train AI models.

Use cases by team

Common first projects in each team: what the AI does, the systems it works in, and how it's measured.

All use cases by team
Support

Replies drafted from your help center

Reads each new ticket and the customer's recent orders, drafts a reply from your help center articles with the source linked, and leaves it for an agent to edit and send.

Works in
Help desks such as Zendesk, Freshdesk or Intercom
Measured by
Time to first reply, and how many drafts go out with few or no edits
Operations

Incoming requests sorted and routed to the right team

Reads requests arriving by email and web form, picks the request type, urgency and owner, fills in the fields and creates the task. Anything unclear goes to a person to sort.

Works in
Shared inboxes and work tools such as Jira, ServiceNow or Asana
Measured by
Requests sent to the wrong team, and time until the right owner picks them up
Finance

Invoices read and matched to purchase orders

Reads PDF and scanned invoices from your accounts payable inbox, pulls the supplier, line items, totals and tax, and matches each one to its purchase order. Mismatches go to a person with the difference highlighted.

Works in
Accounting systems such as NetSuite, Xero or QuickBooks
Measured by
Invoices keyed in by hand, and mismatches caught before payment
Sales

Account briefs drafted from your CRM before each call

The day before a meeting, gathers the account's open deals, recent emails, support tickets and notes into a one-page brief. Every fact links to the record it came from.

Works in
CRMs such as Salesforce or HubSpot, plus email and calendar
Measured by
Prep time per meeting, and facts in briefs that turn out wrong
HR

Policy questions answered from your own handbook

Answers staff questions about leave, benefits and expenses using only your handbook and policies, quotes the section it used, and says it doesn't know when the documents are silent.

Works in
Slack or Microsoft Teams, reading your handbook in SharePoint or Google Drive
Measured by
Repeat questions reaching HR, and answers checked as correct in weekly samples
IT

Access requests checked and prepared for approval

Checks each access request against the person's role and your access policy, prepares the change in your identity system, and waits. Nothing changes until IT approves.

Works in
Identity systems such as Okta or Microsoft Entra ID, with requests from your service desk
Measured by
Time from request to access, and changes made without approval (the target is none)

Trust & security

How your data is handled, in plain words.

Read the full answers
  • 01Your data is used only for your project, and only named people working on it can see it.
  • 02It isn't used to train AI models, and we'll show you the provider settings that prevent it.
  • 03Each system gets the least access its task needs, and that access is removed when the project ends.

Questions

How do we start?

Book a call, or tell us about one job using the form below. If it looks like a good fit, we'll send a short written proposal for a first step, with no obligation.

What does a first project cost?

A first project is usually a Readiness Assessment or a Pilot for one job. Both have a fixed scope and a fixed price, agreed before work starts. After that, cost depends on how many systems the work connects to, how ready your data is, how much risk it carries and how much it's used. See ways to work with us.

How long does a pilot take?

Usually 4 to 8 weeks. The main factors are how ready your data is and how many systems the pilot needs to reach.

Which AI models do you use?

We choose the model for each job, based on what the work needs, and set things up so it can be changed later, for example when a better or cheaper model becomes available.

Is our data used to train AI models?

No. Each AI provider we use is set up so your data isn't used to train its models, and we'll show you those settings.

Can you work with our IT team?

Yes, and we'd expect to. Your IT and security teams can review the design, access and code at each stage, and nothing connects to your systems until they've agreed.

Who owns what you build?

You do. The code, prompts, configuration and documentation are yours to keep, change or hand to another team.

What happens after launch?

We monitor the system against the measure you agreed. From there, we can look after updates, model changes and cost control on a monthly support plan, or hand everything over to your team.

Tell us one job you'd like AI to do

We'll tell you honestly whether AI is the right fit, and what a sensible first step looks like.

One job is enough to start.

We use your details to reply to you, as described in our privacy policy.