Skip to content
Samlution

Work

We would rather show a demonstration than invent a case study.

Client work is published only with permission and verified outcomes. Until then, everything on this page is labelled for what it is: a reference pattern of the systems we build.
Open the live demoDiscuss your project

The reference pattern

What is automated, and where a person takes over

  1. Problem: A new inquiry arrives with the detail needed to qualify it — not just a name and a phone number.
  2. Context: Public research and past material are gathered, with every source recorded on the record.
  3. Draft: Relevant sections are retrieved and assembled into a draft, with gaps marked instead of invented.
  4. Approval: A partner edits and approves. This is the only step that can produce an external action.
  5. Outcome: The approval, the changes and the follow-up task are written to the audit trail.
Every workflow on this page has the same shape: automation handles preparation and evidence, a person handles the commitment. The approval step is what makes the rest safe to automate.

No logos, testimonials or percentage claims appear on this site until a client has approved them and the numbers can be checked. What follows are the structures we deploy.

Prefer something you can click? Six demo builds — five brand sites and one web app — each opens the running site.

See the demo builds
01

Lead to reviewed proposal draft

Consulting firm · 12 peopleIllustrative

The problem

A new inquiry arrives by email. Someone researches the company, looks for a similar past proposal, writes the first draft and sends it days later. The research and drafting steps are repeated for every opportunity.

Pipeline and approval queueDocument retrievalDraft generationAudit log
Related engagement

What we build

  1. 01Capture the inquiry in a pipeline stage with the information needed to qualify it
  2. 02Research step gathers public context on the prospect and records its sources
  3. 03Retrieval step finds the closest past proposal and case material
  4. 04Draft step assembles a proposal skeleton with the missing sections highlighted
  5. 05Approval queue routes the draft to a partner, who edits or rejects it
  6. 06Approved drafts are logged with who approved, when and what changed

Expected outcome

  • A proposal draft prepared before the first call instead of days after it
  • Research and source references attached to the opportunity record
  • No client-facing message sent without an explicit approval

Illustrative pattern — not a measured client result.

02

Internal knowledge assistant with sources

Professional services · 20 peopleIllustrative

The problem

Routine questions — 'what did we agree on scope creep?', 'which template do we use for a fixed-fee proposal?' — go to whoever has been there longest. Answers differ depending on who is asked.

Document pipelineVector retrievalRole-based accessUsage dashboard
Related engagement

What we build

  1. 01Audit the document sources, owners and sensitivity before indexing anything
  2. 02Ingest documents with metadata: owner, type, date and access level
  3. 03Retrieve passages rather than asking a model to remember
  4. 04Return an answer with numbered sources, or an explicit 'not in the knowledge base'
  5. 05Apply role-based access at the source level
  6. 06Log questions, unanswered queries and top sources in a usage view

Expected outcome

  • Routine questions answered with a link to the source document
  • Unanswered queries visible, showing where documentation is missing
  • Restricted material never retrieved for users without access

Illustrative pattern — not a measured client result.

03

Inquiry to booked call

B2B agency · 8 peopleIllustrative

The problem

Traffic arrives on a site that describes everything the agency does. Inquiries land in a shared inbox, get answered unevenly, and booking a call takes several emails.

Landing pagesForm validationCRM pipelineBooking
Related engagement

What we build

  1. 01Rewrite the page around one audience and one outcome
  2. 02Replace the contact box with a short qualification form
  3. 03Route inquiries into pipeline stages with an owner
  4. 04Add calendar booking with pre-call questions
  5. 05Send an immediate acknowledgement and an internal notification
  6. 06Measure conversion from page visit to booked call

Expected outcome

  • Inquiries qualified before a call is booked
  • One visible pipeline instead of a shared inbox
  • Conversion measured at each step, not just at the end

Illustrative pattern — not a measured client result.

Publishing policy

What appears here, and when.

A case study is only useful if it can be checked. That takes a client willing to be named and a measurement both sides accept.
Permission
Written approval from the client before anything is published.
Verified numbers
Metrics traced to a baseline taken before delivery.
Context
What changed, what did not, and what we would do differently.
No composites
We do not blend several clients into one 'representative' story.

Next step

Your process could be the next reference.

If we deliver something worth publishing, we will ask. If not, we will say that too.

Book a Discovery CallSee the live demo

No obligationFixed scope, fixed feeApproval stays human

See how engagements run