StackCraft is a small practice on purpose. I take on four fixed-price AI builds a year. No retainers, no consulting work unless something gets built at the end of it, nothing running longer than six weeks. Most agencies sell you flexibility. I'm selling roughly the opposite of that.
It exists because I missed shipping things. After twenty years inside some of Australia's largest companies, Coles and Telstra and Seek and Disney and Target and Myer and ANZ, I'd built up a lot of strategy documents and not many pull requests. Building software end to end, to a real deadline, for something that actually goes live, is the part I enjoy.
Fixed price is because I don't really have hours to sell, I have finished things to sell. If you want someone for an undefined stretch of time on an undefined problem, you want an employee. If you want a specific feature shipped by a specific date for a specific number, that's what this is.
AI specifically, because nearly every business I talk to is asking the same question about what they should be doing with it, and most of the answers I see out there are either too timid or too reckless. Too timid is a chatbot bolted onto the side of a help centre. Too reckless is a model dropped into a workflow nobody trusts yet. The useful work is usually somewhere in between.
Four a year, because each one gets four to six weeks of me building it end to end. There's no team to spread across more clients. The cap isn't a marketing thing, it's just how many of these I can do properly.
What I take on is AI feature builds, where one capability goes into a product that already exists, AI MVPs, where it's the first version of something new, and internal AI tools built for your team rather than your customers. All fixed price, all scoped before anyone signs anything.
What I don't take on is monthly retainers, design subscriptions, brand work, anything without a single decision-maker, and AI-for-the-sake-of-AI projects with no real user at the end. The full list is on the How I Work page.
If you've got a defined thing you'd like built, the contact form is the right place to start. If you're here for the build-in-public side of it, the changelog and these articles are where I'll be honest about how it's actually going.