Proof & Examples

Public branches, product mockups, and honest workflow examples.

This first proof pass links to live public work, shows code-native mockups, and keeps sample trade scenarios clearly labelled until real customer screenshots and videos are captured.

Proof assets

What can be opened today.

Current Control shows the separate marketing website pattern. OOAKF shows app-hosted customer tools. The sandbox shows the C-module product shape using dummy data only.

Open sandbox demo

Live public site

Current Control public website

Current Control

A live customer-facing branch kept separate from the MINDMATRIX customer app host.

Proof role: Shows the public website pattern for a customer with an established marketing presence.

  • Marketing website remains separate from app-hosted modules
  • MINDMATRIX app host can carry focused customer tools
  • Useful proof for the tenancy split and public presentation model
Open Current Control

Customer app tool

OOAKF PAX tool

One of a Kind Fronts

A public app-hosted tool that demonstrates customer-facing module delivery under the customer app host.

Proof role: Shows how customer tools can live under /tools/{module} without changing the main brand site.

  • Customer app host public tool
  • Guided customer workflow rather than generic website content
  • Clear pattern for app-first modules under the MINDMATRIX host
Open PAX tool

Sandbox

C-module sandbox demo

MINDMATRIX

A static, dummy-data tour of the C-module operating system with no live AI or integrations.

Proof role: Lets prospects understand the shape of the product before real customer setup work begins.

  • Dummy customer thread, quote preview, and onboarding checklist
  • No API, provider, payment, email, WhatsApp, banking, or supplier calls
  • Useful as a sales demo while real screenshots are captured later
Open sandbox demo

Code-native product proof

Mockups first, captured assets later.

These screens are intentionally illustrative. They help explain the workflow now, while an approval-stage asset pass can replace them with real screenshots and videos later.

Real screen examples

We show simple screens and before-and-after examples so you can see what the setup does without pretending every example is a polished client story.

  • Example lead summaries
  • Example intake screens
  • Before and after lead journeys

Straight talk about what changes

The point is to show where trade businesses lose work and what a cleaner setup looks like in plain English.

  • Why missed enquiries cost real work
  • Why slow quoting is usually a process problem first
  • Why better follow-up means more sales and less evening admin

Example setups for common problems

These examples stay honest: typical problems, likely fixes, and the sort of results a better setup is meant to create.

  • Missed WhatsApp leads pulled into one list
  • Vague quote requests turned into cleaner briefs
  • Team handover, routing and booking steps tightened where needed

What this looks like

Example lead summary

Quote-ready
New lead
Business typeWest London electrician
SourceWhatsApp + web form
JobConsumer unit quote
PostcodeW5
Photos4 attached
AccessAvailable next week

What the setup does next

  • Sends a quick first reply
  • Asks for the missing details before quote time is used
  • Marks the lead as ready for pricing and follow-up

Quote intake

Example quote summary

Needs approval
Contact confirmedYes
Scope capturedKitchen tap replacement
Target responseSame day
Follow-up48 hours after quote

Before / after lead handling

Before

  • WhatsApp lead buried under site messages
  • Postcode and photos missing
  • Quote delayed until late evening
  • No structured follow-up after sending

After

  • Lead acknowledged quickly
  • Missing details collected up front
  • Estimator sees a quote-ready summary
  • Follow-up is scheduled before the lead cools

Hypothetical scenarios

Common bottlenecks and the kind of setup that can fix them.

These are example workflows, not named client case studies. They keep the promise grounded while the proof library is built.

Hypothetical scenarioGrowth

Example workflow: from scattered enquiries to one clear intake

Small handyman business | South East England

Problem

Website forms, missed calls, and WhatsApp messages were all being checked at different times, so some jobs were missed and some were replied to too late.

What Mind Matrix would set up

An assisted Growth setup that connected the useful lead routes, acknowledged new leads, pulled the basic job details into one place, and kept unanswered enquiries visible.

Before

Lead handling depended on memory and whatever messages could be chased in the evening.

After

Every enquiry had a clearer starting point and fewer jobs were lost simply because the first reply was too slow.

What you gain

Better enquiry visibility and less time spent wondering which lead had already been answered.

Request a similar demo call
Hypothetical scenarioConvert

Example workflow: turning vague messages into quote-ready briefs

West London electrician | West London

Problem

The business was getting solid enquiries, but quote turnaround depended on chasing missing photos, scope details, and access notes after first contact.

What Mind Matrix would set up

A lead-to-quote workflow that collected missing details earlier, prompted for photos, and produced a cleaner brief before pricing time was used.

Before

Strong leads often sat for too long because the quote could not be prepared properly until late in the day.

After

New enquiries were qualified faster, the right job details were gathered earlier, and more leads stayed active long enough to quote properly.

What you gain

A cleaner route from incoming enquiry to quote-ready job without needing office staff too early.

Request a similar demo call
Hypothetical scenarioConvert

Example workflow: reducing evening admin with better lead handling

Property maintenance company | Greater Manchester

Problem

A steady stream of maintenance requests was coming in, but the team struggled to tell which enquiries were worth pricing and which still needed chasing.

What Mind Matrix would set up

Lead qualification rules, clearer intake prompts, and follow-up reminders that kept worthwhile enquiries moving without relying on memory.

Before

Estimator time was being burned on low-quality or incomplete enquiries, while admin kept spilling into evenings.

After

The team could filter faster, quote the better jobs sooner, and keep worthwhile opportunities moving with follow-up built in.

What you gain

Less wasted admin time and a stronger conversion path from enquiry to booked work.

Request a similar demo call
Hypothetical scenarioComplete OS

Example workflow: joining up lead handover and booking

Bathroom fitter | Home Counties

Problem

Higher-value enquiries needed a more professional process, clearer internal handover and better visibility between first contact, site visit and booking.

What Mind Matrix would set up

A Complete OS rollout with richer intake, internal routing, clearer next steps, and staged implementation around the team process.

Before

A lot of the customer journey depended on manual coordination and ad hoc admin.

After

The business had a more polished front-end process and better visibility over where each enquiry sat.

What you gain

A more professional sales journey for higher-value work and less reactive admin at every stage.

Request a similar demo call

Next step

Show us your version of the problem.

We will show you which package fits, what the first fix should be, and which C-modules matter first.