Muhammad Umar Farooq

Workflows

Drive the workflow before you buy it.

Four systems, running on invented sample data in your browser. No account, no personal data collected, and nothing is ever sent to anyone — every one of them stops at a person.

Proposal from a discovery call

Interactive demo

A first-draft proposal, built from the call and your own approved material, waiting for a person to approve it.

Sample data, invented for this demo. No account needed, no personal data collected, and no real message, email or CRM record is created.

  1. Harbourline Freight
  2. Read the brief
  3. Extract requirements
  4. Select approved material
  5. Draft the proposal
  6. Approve and save to CRM
Sample input
RAY (Harbourline): …so the bottleneck is the quote desk. Three people, and
every quote starts from a blank page even though ninety per cent of what goes
in it is the same.

YOU: How many quotes a week?

RAY: Forty, maybe fifty in peak. Each one is forty minutes of someone pulling
rates out of the TMS and retyping them. Then it sits waiting for Priya to sign
it off because she's the only one who checks the fuel surcharge.

YOU: And if the surcharge is wrong?

RAY: We eat it. Happened twice last quarter. That's the bit that actually
costs us.

YOU: What's the deadline?

RAY: We want it before peak season. That's the first week of March. Budget is
somewhere in the thirty to forty range, and I have to take it to Deborah.

Pick a sample and run the workflow to see what the system extracts.

Meeting notes to CRM record

Interactive demo

A call ends and the CRM is already up to date, with the salesperson approving what gets written.

Sample data, invented for this demo. No account needed, no personal data collected, and no real message, email or CRM record is created.

  1. Meridian Dental Group
  2. Read the transcript
  3. Summarise
  4. Extract actions and stage
  5. Prepare the update
  6. Approve and update CRM
Sample input
YOU: …so where did you land after speaking to the other two?

JUNE (Meridian): Honestly you're ahead, but Caleb wants to see the migration
plan written down before we commit. He got burned on the practice-management
switch two years ago.

YOU: That's fair. I can have that over by Thursday.

JUNE: Thursday works. The other thing is pricing — we're a group, six sites,
and your page quotes per-site. Is there a group number?

YOU: There is. I'll put both options in the same document.

JUNE: Good. If Caleb's happy with the migration plan we'd want to start in
January. Our financial year starts February so it has to be signed before then.

YOU: Understood. Who signs?

JUNE: Caleb signs. I recommend.

Pick a sample and run the workflow to see what the system extracts.

Assistant over internal documents

Interactive demo

Answers drawn only from approved internal documents, with the source shown — and a refusal when the answer isn't in them.

The three documents below are the assistant's entire knowledge base, invented for this demo. No account needed, no personal data collected.

Knowledge base — 3 fictional documents

  • Internal · last updated 12 Jan

    Before kickoff

    Signed order form filed against the account. Access request sent for the client's mail and CRM. A named approver is recorded on the account before any workflow is switched on — no build starts without one.

    Week one

    Kickoff call, then process mapping with the people who do the work rather than their manager. The output is a written map the client signs off before anything is built.

    Going live

    Workflows run in review-only mode for the first two weeks. Nothing sends automatically during that window.

  • Internal · last updated 3 Feb

    Legal — email automation

    US law firm. Routine client, court and counsel email went from 7–10 minutes per reply to 1–2 minutes to review and send. Approved for external use.

    SaaS — not yet available

    No approved SaaS case study is currently in the library. Pending client sign-off.

  • Internal · last updated 20 Jan

    Engagement shapes

    Fixed price per build, or hourly for ongoing work. The figure is agreed before work starts.

    Scope changes

    A change in scope is re-quoted in writing before it is started, never absorbed silently.

Ask a question

  1. Parse the question
  2. Search approved documents
  3. Check the passages support an answer

Pick a question. One of the three has no answer in the documents.

Lead research and outreach draft

Interactive demo

A researched account and a first-draft email that references something true, stopping at a person before it goes anywhere.

Sample data, invented for this demo. No account needed, no personal data collected, and no real message, email or CRM record is created.

  1. Verden Logistics
  2. Pull company facts
  3. Identify likely pain
  4. Find a trigger
  5. Draft the outreach
  6. Approve draft for sending
Sample input
Verden Logistics — fictional target account

Sector: regional freight and warehousing
Headcount: 180, up from 140 last year
Footprint: four depots
Systems in public job ads: TMS, a WMS, and a separate CRM
Recent public activity: hiring two "customer operations coordinators"
Leadership: operations director has posted twice about on-time delivery rates

Pick a sample and run the workflow to see what the system extracts.

What you are looking at

These run entirely in your browser on invented data. There is no model behind them: each sample produces the same result every time, so what you see is what the next person sees. No message, email or CRM record is created by anything on this page, and none of the companies named exist.

What is real is the shape: every one of these workflows stops at a person before anything leaves the building. That is the part worth evaluating. The case studies cover systems that actually ran.

Walkthroughs

See the systems in action.

Four workflows, each one ending with a person approving what happens next. Every walkthrough is written out in full, so you can read it rather than watch it.

2 min

Proposal from a discovery call

Recording in progress — read the walkthrough below

Proposal from a discovery call

A first draft exists before the call notes go cold, and a person approves it.

  1. 1.A proposal request arrives, as a call recording or a written brief.
  2. 2.The system extracts the requirements: the problem, the volume, the constraint and the deadline.
  3. 3.It selects from material you have already approved, rather than writing new claims.
  4. 4.A first draft is assembled in your format.
  5. 5.A team member reads it, changes what is wrong, and approves it.
  6. 6.The CRM is updated and the follow-up is scheduled. The client is sent nothing until a person sends it.
Book a workflow assessmentTry the interactive version

2 min

Meeting notes to CRM record

Recording in progress — read the walkthrough below

Meeting notes to CRM record

The CRM is current by the time the salesperson closes the laptop.

  1. 1.A sales call ends and the transcript lands.
  2. 2.The call is summarised in the firm's own language, not the model's.
  3. 3.Action items, deal stage, next step and follow-up date are extracted as separate fields.
  4. 4.The salesperson reviews the draft and corrects anything the system read wrong.
  5. 5.On approval the CRM is updated and the follow-up is scheduled. Nothing is sent to the client.
Book a workflow assessmentTry the interactive version

2 min

Assistant over internal documents

Recording in progress — read the walkthrough below

Assistant over internal documents

Staff get answers with sources, and a clear refusal when the answer isn't there.

  1. 1.An employee asks a question in plain language.
  2. 2.The system searches only the documents you have approved for it.
  3. 3.The answer comes back with the passage it came from, named and quoted.
  4. 4.The employee opens the source document to check it.
  5. 5.Asked something the documents don't cover, the assistant says so instead of inventing an answer.
Book a workflow assessmentTry the interactive version

2 min

Lead research and outreach draft

Recording in progress — read the walkthrough below

Lead research and outreach draft

Outreach that references something true, reviewed by a person before it sends.

  1. 1.A target account is selected from the list.
  2. 2.Public company signals are collected: size, systems, hiring, recent activity.
  3. 3.A likely pain point is identified and stated with its confidence.
  4. 4.A personalised draft is written around that one specific thing.
  5. 5.A salesperson reads, edits and releases it. The system never sends on its own.
Book a workflow assessmentTry the interactive version

Losing hours to work an AI system could handle?

Tell me about the process. I'll tell you straight whether it's worth automating — no pitch, no obligation.

Book a call