Skip to main content

Built to order

Some tools we build for one client's need. Here are two.

Each built for a client.

Feedback, in people's own words

People answer a few questions in a short conversation, by voice or in writing, and you get a clear written summary, in your language.

Tell people who will read the summary before they answer.

Built for a client.

What people said after the sales training

In their words
“More real cases, fewer slides.”
“The pricing part came too late in the week.”
Asked for
A short follow-up session a month later.
Illustration. Example summary, written for this page.

A weekly digest from your own documents

Every Monday, what changed in your documents, written up as a few short posts. Each one quotes its source, and nothing goes out until someone on your side approves it.

The person who approves it chooses who sees each post: the whole company or one department.

Built for a client's operations team.

Monday digest

What changed
Bookings above the travel limit now need a second approver.
From the source
Travel policy, section 4: “Bookings above the limit need approval from a second manager.”
Approved
By your comms lead, before anyone saw it.
Illustration. Example digest post, written for this page.

How we build to order

  • The people involved are told first, and choose whether to take part.
  • Each output goes to the person it is about, or to the team that asked for it.
  • It is not for evaluating people, and our customer terms say so.
  • It does not read emotions, and it never infers anyone's origin or background.
  • A person on your side approves every output before anyone sees it.
  • Every output is marked as written by AI.
  • Read the privacy notice (opens in a new tab).

Tell us what you want to hear about

Bring one situation to a demo, and we will show you what we would build for it.