Most agencies have a process page. Most process pages are four icons and the words "discover, design, develop, deliver".
Here's ours properly, including the parts that are unglamorous.
01. Get to know it
We start by understanding your business, your audience and what the project needs to achieve.
Not a branding workshop with sticky notes. Actual questions: how you make money, who buys from you, what your team does forty times a day that a system could do once, what happened last time you tried this.
What you'll see: a written brief that says back to you what we think the problem is. If we've misunderstood something, this is where it's cheap to find out.
02. Work it out
We define the structure, user journeys and technical requirements. This is also where design and development thinking come together, rather than one handing over to the other.
That matters more than it sounds. Plenty of studios design something beautiful, hand it to developers, and let them discover it can't be built to budget. Kryspin is in these conversations from the start, so what gets designed is what gets built.
What you'll see: sitemap, wireframes, and a straight conversation about anything with a nasty technical shadow.
The most expensive decisions on a project are made in week two, by people drawing boxes. Get that wrong and no amount of polish saves it.
03. Make it
Design and development work closely throughout. We prototype, build and test as we go.
No six-week silence followed by a big reveal. You see it as it comes together, on a real URL, on your own phone.
What you'll see: a staging link from early on, regular check-ins, and honest updates when something takes longer than we thought. Sometimes it does.
04. Put it to work
Once everything is properly tested, we launch. Then the real information starts arriving.
Launch is the middle of the project, not the end. Analytics tell you what people actually do, which is reliably not what everyone predicted in week one. We'd rather be there for that part. 88% of our clients carry on working with us afterwards, which is the number we're proudest of.
What you'll see: a launch that isn't dramatic, then data, then sensible changes based on it.
Who you actually work with
Two founders, both hands-on. Luke on design, UX and strategy. Kryspin on architecture, code and infrastructure. Between us and the team, 55+ years of combined experience and 34+ projects launched.
You won't be sold to by a director and then handed to someone you've never met. That's the whole reason we set the studio up the way we did.
Where projects go wrong
In our experience, almost always one of three:
- Nobody agreed what success looks like. Stage one exists to prevent this.
- Design and build were separate. Handover is where budgets die.
- Content arrived last. The single most common cause of a delayed launch, every time.
If you want to see what it looks like at the other end, have a look at TableCloud: brand, naming, UX and custom software, all from one team. Or just tell us what you're planning.
