Products · Bespoke builds

A tool built for exactly how you work

When off-the-shelf doesn’t fit, we build one on the Opafex platform around your workflow. You own the product.

A separate engagement from the audit, and most audits don’t lead to a build at all.

Book a scoping callOnly want the result? →

Case studies

Two builds we have delivered

Both started the same way — understanding the work before writing anything. Client names are withheld under NDA.

Candidate CVs into the firm’s house format

UK recruitment agency

Consultants rebuilt every incoming CV into the firm's template by hand. Each took hours, and no two came out the same.

In

  • The candidate’s CV
  • The consultant’s interview notes
  • The record already held in their CRM

What happens

  • 1Extract every field, mark gaps pending
  • 2Fill the firm’s fixed house template
  • 3A consultant reviews and signs off
  • 4Render and deliver

Out

  • A finished DOCX
  • A matching PDF
  • Emailed to the client, on a person’s say-so

The decisions that mattered

  • The system never invents a field and never leaves one blank. Anything the sources do not answer waits for a human as pending.
  • Only a person can set the signed-off status. The system refuses while any required field stays unresolved.
  • Every value shows which document it came from. Anything left out shows why, and you can reverse it.
  • Corrections teach it. Its own output never does, so a mistake cannot harden into a rule
  • Candidate-side and client-side staff see different data. The server enforces the split.
  • You can erase a candidate completely, down to the original uploads.

Where it stands

The extraction engine has proven itself end to end on real candidate CVs. The review, access and delivery stages now enter daily use.

Answers from the rulebook or says it cannot

Specialist supplier

Customers asked rules-based questions whose answers sat deep in the documentation. Staff answered the same ones repeatedly, and generic website chat handled none of them.

In

  • The company’s own documentation
  • The owner’s written brief and voice

What happens

  • 1Reads the whole knowledge base
  • 2Answers only from those sources
  • 3Refuses when the documents are silent

Out

  • An answer, with the source it came from
  • Or an honest “not in our documentation”
  • The enquiries worth following up

The decisions that mattered

  • It reads the whole knowledge base on every question. It cannot deny something sitting in its own documentation.
  • The owner's brief replaces the default persona instead of stacking underneath it. Their instructions win.
  • The brief never relaxes two rules. Facts come only from the supplied sources, and it never discloses its own configuration.
  • We configured everything from our side. The customer had nothing to set up.

Where it stands

Live on their site, it answers from their documents with citations. We verified it refuses questions its sources do not cover.

Neither of these started as a build brief. Both started with understanding the work — The audit answers that..

When a build is the right answer

Much of the time a build is the wrong answer. We say so.

A build suits work a machine can do, with a person signing off. We only build what we know we can deliver.

How a bespoke build happens

A fixed-scope path from your workflow to a product you own.

01

Scope

We sit down with the actual work. Inputs, rules, edge cases and what good looks like get agreed up front.

02

Build on the platform

We assemble it from the Opafex engine. It inherits everything the platform already does.

03

You run it

It lands in your account as a product. You drive it from the dashboard or plain-language chat.

04

It improves

New rules, new inputs, new outputs. It evolves with your process, without a rebuild.

Why build it on Opafex

A bespoke build here isn’t a throwaway script. It stands on the same production platform we run everything else on.

Grounded, not guessing

It verifies every write against real results. It asks before anything risky.

The whole platform underneath

Dashboards, durable execution, connection health and a knowledge grid built in — not a thin script you’ll outgrow.

Connects to what you already use

58 providers come built in, and we connect any system with an OAuth API. REST, MCP and SDK bridges cover the rest.

Evolves without a rewrite

Change the house style, add a data source or adjust the rules. The build adapts without starting over.

More we can build

Live

CV / document formatter

Learns a firm’s house style and reformats any document into it. Exports polished DOCX and PDF.

A CRM shaped to your pipeline

Your stages, your fields, your rules — with the agent keeping it current.

Client-reporting console

Per-client dashboards and reports generated on request from your connected tools and data.

Inventory / operations console

Structured tables, scheduled checks, and event triggers that keep stock and orders moving.

Document pipeline for any doc type

Contracts, proposals and reports come in. They go back out in your standard format.

Not on the list? That’s the point of bespoke. Tell us what you need.

Bespoke builds

Bespoke builds

Describe the tool you wish you had

Tell us the workflow that eats your time. We quote a fixed price and build a product you own.

Book a scoping call