01 Question and journey
We start a case-study record with the business question and the customer journey.
Work / Evidence ledger
Work, with context.
A useful case study explains the starting problem, Aaron’s role, the work that was delivered and the evidence available.
This page sets out the current record and its limits. Publication context does not establish Aaron’s role or a client result.
How to read the work
Specific context is more useful than a row of uncheckable claims.
02 Role, scope and limits
We name the role, scope and limits before describing the work.
03 Observation and explanation
We separate an observed change from an explanation of why it may have happened.
04 Private context
We keep private client context off a public record unless its inclusion is authorised.
The evidence ledger
Publication context, training and client work stay separate so the record does not imply more than it can show.
| Category | Record | What it covers | Evidence boundary |
|---|---|---|---|
| Publication context | TripCanvas | TripCanvas is a travel publication. Its public About page provides context for the publication; Aaron’s role is not established by that source. | The linked source does not verify Aaron’s responsibilities. This preview makes no claim about his role, a Multiplier Engine client engagement or traffic, rankings and revenue results.TripCanvas publication context |
| Training and team context | Shared reviews and handovers | Some scopes include a workshop, a working session or documentation that helps an existing team carry the next step forward. | Internal context only. The format, participants and deliverables depend on the agreed scope; this page does not present a public training catalogue. |
| Client work | No public case study claimed yet | A client record belongs here only when the starting question, role, work and evidence can be shared with permission. | There are no client names, logos, testimonials or performance figures on this preview. A scoped conversation can establish whether a publishable record is appropriate. |
The TripCanvas source describes the publication’s purpose and history. It does not establish Aaron’s role; this page presents publication context without claiming employment, a client engagement or performance results.
Questions about this work record.
What counts as evidence on this page?
A source you can check, tied to a stated starting question, role and piece of work. Each record also states what its source cannot establish.
Does the TripCanvas publication link establish Aaron’s role?
No. It provides context for the publication. The linked source does not verify Aaron’s responsibilities or a Multiplier Engine client engagement.
Does the TripCanvas link prove a marketing result?
No. The link provides publication context and does not prove traffic, rankings or revenue results.
Are there named client case studies here?
No. The current ledger does not publish client names, logos, testimonials or performance figures.
What permission is needed before a client record appears here?
The client’s permission for the project information we include, alongside permission to share the supporting evidence. Client identity and private context stay off this page unless their inclusion is authorised.
Does a recommendation prove the result improved?
No. A recommendation, an implemented change and an observed outcome need separate evidence.
Are workshops listed as a public training catalogue?
No. The current record describes possible scoped working sessions or documentation, rather than a public course catalogue.
What would a fuller case study need?
A defined starting problem, role, delivered work, evidence that can be shared and clear limits on the outcome claim.
Can I use an illustrative service example as client proof?
No. Illustrative examples explain a decision or scope; they do not establish a completed client engagement.
Where can I discuss relevant work for my project?
On our Contact page. Tell us about your problem and the evidence or decision you want to review.