Selected work

The situation.
The solution. The result.

A closer look at the work, with the evidence and delivery boundaries kept clear.

Selected case studies

Business problems. Practical solutions.

A closer look at our founder’s work: the situation, the solution and what changed. Company names are kept confidential.

Trading business · AI workflows

The next sales meeting starts with context.

Sales preparation drew on past meetings, company documents and task updates. A dedicated AI workspace brought that history together, with source-linked agendas, decisions and reusable instructions.

The result

13 dated meeting briefs in one sales workspace, with the evidence behind each agenda.

Read the case

The challenge

The business context sat across different records. A useful AI answer needed the relevant meeting history, current decisions and company information together.

The approach

A dedicated sales workspace connected meeting briefs, preparation pages and task context. Company-specific AI routines defined how to handle presentations, meeting intelligence and market insight.

What changed

The completed workspace contained 20 pages, including 13 dated meeting briefs. Meeting preparation had a defined starting point and a route back to its sources.

A supervised working setup, with manual refresh. Wider team adoption remained a separate step.

Trading business · Management reporting

Two departments. A clearer business picture.

Sales and operations held different parts of the story across meetings, task lists and finance records. Two internal dashboards brought those sources into readable views of priorities and follow-ups.

The result

Two published dashboards, each with five views and links to the supporting evidence.

Read the case

The challenge

Leadership needed to read departmental activity alongside the underlying records, without treating incomplete or conflicting information as fact.

The approach

Sales and operations dashboards combined dated meeting records, task registers and selected finance data. Filters, priority views and source references made the information easier to explore.

What changed

Both dashboards were published internally and checked across all ten views on desktop and mobile. Unknown outcomes stayed visible as unknowns.

Published snapshots of dated records. Automatic refresh was outside the delivered scope.

European manufacturer · Operational diagnostic

A customer promise with no way to verify it.

A response commitment passed through more than 150 outside partners, but the company could not verify the outcome. Tracing one enquiry across four systems and four regions revealed the missing feedback path.

The decision

Ten findings: eight could use existing fields or processes; two required new work. No core-system replacement was needed.

Read the case

Chemical trading company · Banking profile

A clear business story for banking review.

The company’s licence and letterhead established its identity. Its banking profile also needed to explain what it traded and how the business worked. A concise document brought the verified facts and trading model together.

The result

A one-page business profile, with an editable source and a checked PDF prepared for banking review.

Read the case

The challenge

Official company records established the legal facts, while the business explanation needed to connect the licensed activities with its local and international trading model.

The approach

The profile combined a company overview, licensed activities, trading model and intended account use. The existing identity was retained, and every factual claim was checked against the supplied records.

What changed

The business had a complete, readable A4 profile in Word and PDF, with the company information and commercial explanation in one place.

Delivered for banking review. Bank approval was outside the engagement.

Inside one diagnosticThe evidence, the decision and the scope

Fix the missing return path.

An earlier operational engagement shows how we separate existing fixes from the work that actually needs building.

ANONYMISED ENGAGEMENTONE REAL ENQUIRY

Four systems. Four regions. Ten evidenced findings.

A European manufacturer was issuing a written response promise through more than 150 outside partners. The work was assigned, but its outcome was recorded nowhere the company could verify.

SCOPE DECISION10 EVIDENCED FINDINGS
REUSE8

Used fields or processes already available

BUILD2

Needed anything new to be built

REPLACE0

Required the core system to be replaced

What happened next: the two-page decision brief went into the client’s internal approval meeting.

DECISION RECORD / 01ENGAGEMENT SUMMARY

THE OPERATING PROBLEM

A customer commitment was being issued at scale. Its outcome was recorded nowhere.

  1. 01
    OBSERVED

    Ownership was recorded at assignment. No reliable return path showed whether the promised response happened.

  2. 02
    CONSEQUENCE

    The accountable team could not confirm the result, defend the spend, or answer the complaint with evidence.

  3. 03
    DECISION

    Fix the return path before replacing the system.

USE NOW

Fields, deadline, and reporting view already exist.

BUILD ONLY

Proof of contact and a monthly return loop.

NOT REQUIRED

Core-system replacement, broad migration, or unapproved access.

EVIDENCE REFERENCES ATTACHED TO EVERY FINDINGOWNER + NEXT STEP
Explore the diagnostic option →
Put your existing AI tools to work

Make your AI subscription work for your business.

Show Yasir the tools you use and where the work gets stuck. Agree a practical starting point, from a founder’s AI workspace to a connected team workflow.