Case studies
None yet, and we are not going to pretend otherwise.
GrayMatter has no customers yet. Rather than fill this page with hypothetical scenarios dressed as client work, here is the format the first real one will take, so you can hold us to it.
The format
Eight sections, including the two most companies leave out.
Constraints and lessons are what make a case study useful to the next buyer. A page of results with no constraints is an advertisement.
-
Client and industry
Named with permission, or described by sector where the client prefers not to be named.
-
Problem
What was slow, manual or missing, in their words rather than ours.
-
Constraints
Budget, timeline, systems that could not be touched, people who had to keep working throughout.
-
Approach
What the prototype proved, what it disproved, and what was scoped from the feedback.
-
Architecture and technology
What was built, what it integrates with, and why those choices.
-
Implementation
How it went live, including what went wrong on the way.
-
Result
The measure agreed before the work started, reported whether or not it flatters us.
-
Lessons
What we would do differently. If there is nothing, the case study is not finished.
What will never appear here
Four things we will not do on this page.
- A client named without their written approval.
- A number we did not measure against a measure agreed before the work.
- A logo wall of companies we have not worked for.
- A "case study" that is really a product brochure with a client's name attached.
Until then, judge us on the prototype
The honest substitute for a case study at this stage is a working prototype on your own workflow, in hours, at no charge. You can judge the work rather than the write-up.
See also how we work, the questions people ask and where we are as a company.