AI features, MVPs and internal tools for tech companies.
Scoped up front, priced before we start, and finished in four to six weeks. One person on your feature, MVP or internal tool from first call to handover, and nothing rolling on afterwards.
Five ways I work.
Pick whichever one matches your problem. If none of them do, I’ll say so.
How a build usually goes.
One scoping call, a price in writing, and working software in your codebase within weeks. No retainers and nothing rolling on afterwards.
Scope
One call to get specific about the problem and what finished actually looks like. Then a fixed price, in writing.
Build
I build it myself, end to end. The scope is locked, and anything that changes gets agreed before I touch it.
Ship
Working software handed over in four to six weeks, and then I’m out of your way.
Things I’ve built myself.
Products of my own, shipped and in front of real users. Part of the reason I only take on a handful of client builds a year.
Chris Jack.
Design and AI leader. StackCraft is the client work. The products are the longer bet.
I’m Chris. Twenty-two years in senior product design roles at WooliesX, Coles, Catch, Myer, Target, Seek, Disney, Telstra, MYOB and ANZ. Once the AI tools got good enough to change how I work, I went back to writing product code instead of leading the teams who write it, which is the part of this job I actually missed.
StackCraft is a small practice on purpose, a handful of fixed-price builds a year for companies who want one person on their feature, MVP or internal tool from start to finish.
For the design-leadership side of what I do, including the folio and the employment history, see chrisjack.au.
