Marketing · Create module
We do great work and have no case studies
Buyers want proof from jobs like theirs. Why case studies never get written in busy firms, and how to draft one from a real job, with the customer’s yes.
Starts on One module · Create · $350 a month
In your words
Last year we moved a food manufacturer’s whole production line over one weekend, with zero lost shifts. The plant manager called it the smoothest move they’d ever had. We have the photos, the schedule and his email. None of it is on our website.
When a new prospect asks “have you done something like this before?”, our estimator digs through his phone for pictures and forwards an old thread. It works on a good day, but the prospect who never asks just sees a site that says we are “committed to quality”.
Why it happens
A case study needs a writer, a customer’s permission and a quiet afternoon, and all three arrive at different times. By the time anyone thinks of it, the job is months old, the details are fuzzy and asking the customer feels awkward.
There is also a real worry about saying too much. Customers in manufacturing and distribution often don’t want their name, their volumes or their plant on a supplier’s website, so the safest thing seems to be publishing nothing at all.
What it costs
Without proof, every sales conversation starts from zero. The buyer has to take your word for it, and when two suppliers look alike, the one that shows a job like theirs usually gets the next call.
Your best work also goes uncited. An assistant asked who has done a weekend line move in your region has no page from you to point to, even though you did exactly that.
How Humonix fixes it
01Agent
Start from a real record
A case study is drafted only from a real record (a signed-off job, a paid invoice or a won deal) and the customer’s own words, such as a reply they sent you or a review they wrote.
02Agent
Keep it private first
The first draft is private to your team. Every sentence cites one of those facts; no number, result or quote is added that the record doesn’t hold.
03Agent
Ask the customer, part by part
The customer says yes separately to each part: the case at all (anonymised), their name, their words and the result. You see exactly what they agreed to.
04Agent
Publish only what they agreed to
The public version carries only the parts the customer granted, goes on your site after your approval, and can feed posts and the newsletter.
01Agent
The department
The Create module drafts the case study and tracks each customer’s permission. It is in early access and run with Head of Digital.
02Hue
Hue’s part
Hue can point a visitor who asks “have you done this before?” to the published cases, and only to those.
03You
Your yes
Nothing becomes public without two yeses: the customer’s, recorded part by part, and yours on the final version.
What you see
Value: the month’s finished jobs and paid invoices, the records a case study can be drafted from.
Where to start
One module · Create
One of twelve modules, run end to end by agents; you approve what goes out. No person included. Month to month.
Questions
What if the customer won’t be named?
Then the case can still be published anonymised, if they agree to that much, describing the work and the result without their name.
Can it invent a result to make it stronger?
No. A case study states only what the record and the customer’s words hold. If there is no measured result, the page doesn’t claim one.
How long does it take us?
A few minutes to pick the job and approve the draft. The customer’s permission is asked by email from your side, with the exact parts listed.