Inkwell
Someone close to me is a tattoo artist. I watched her try to manage a studio with booking tools never built for how a tattoo studio works.
Designed and built solo · 2026
- My role
- Everything, solo
- Team
- Built with Claude Code and Claude Design
- Years
- Live since June 2026
- Outcome
- Adopted by three Singapore studios
01 The full story
Identifying a gap in what current products offer, and building a complete product on my own around the specific needs of a niche market.
The brief
Someone close to me is a tattoo artist. I watched her try to manage a studio with booking tools that were never built for the way a tattoo studio actually works.
So I built a product shaped specifically for tattoo studios and the artists in them, around their real tasks and work patterns, and flexible enough for both studio managers and artists.
My role
I designed and built Inkwell on my own, end to end: research, product definition, interface design, front end, back end, the release itself, and the updates that followed from user feedback. It is used daily by three studios today.
Working solo was only possible because of AI tools. Claude Code and Claude Design were the main ones, with parallel checks run by agents on ChatGPT. That setup is what let one person deliver something that holds up to daily use.
- 04.A
The importance of a good UX approach in the AI era
AI has made it possible to build a product quickly. Most of what gets built that way sits unused, with no real user adoption.
The reason is rarely the code. It is that nobody understood the people it was meant for, and building fast makes that the easiest thing to skip.
Inkwell started from watching one artist run a studio, not from a feature list.
- 04.B
Making a modular product that is easy to update
Inkwell was not built in one shot. It is several modular systems that interact, each solving a different need, working together.
That structure is what makes it fast to upgrade. Feedback can turn into new functionality without touching the core, so the product keeps evolving without every change putting the rest of it at risk.
This was the biggest learning about what makes an AI built product last.
- 04.C
Keeping the AI in the build, not in gimmick features
The easy mistake would have been to put AI inside the product because AI was used to build it.
That is building for the hype rather than for the people using it. A studio needs to take bookings, collect deposits and know where its money is. None of that is waiting for an AI model. It is waiting for someone to take it seriously.
So Inkwell is built and maintained with AI, and the daily use of it is AI free. What is in the product came from what users actually asked for, not from chasing hype around AI features.
- 04.D
Adoption
Word of mouth between artists is what spread it, and that is what led more studios to take Inkwell on as their main studio tool.
Its design and architecture made it straightforward to adopt without extra costs, a welcome change from the subscription tools studios are used to.
- 04.E
Next steps
It is not a priority, but the feedback and the usage raise an obvious question: whether to market it properly and build a business plan for wider adoption, beyond Singapore.
The product scales without much difficulty. What the next step should be is still open.
02 Ownership
What I did, and the tools I used.
Fig. 00 How it is built
Several modular systems that interact.
Feedback from the studios becomes new functionality without touching the core. That is my biggest learning about what makes an AI-built product last.





Home screen · Sample data
03 Decision map
The decisions, and why.The pivotal decision.
Four decisions I made in this work, and how or why I made each one. Where a figure shows the result, it is linked.
-
01
ChoseStart from watching one artist run a studioInstead of
Starting from a feature listWhyI saw someone close to me missing a tool made for her specific way of working, so her real day became the brief. Most products built quickly with AI sit unused, because nobody understood the people they were for.
-
02
ChoseSeveral modular systems that interactWhy
So feedback becomes new functionality without touching the core.
-
03
ChoseKeep AI in the build, not in the productInstead of
AI features in the productHowBuilt and maintained with AI; daily use is AI-free.
WhyA studio needs to take bookings, collect deposits and know where its money is. None of that is waiting for an AI model.
-
04
ChoseData stays local to each studio, with email as the backupWhy
There is no server bill and studios own their records.
04 Evidence
The product.
Select a figure to open it larger.
Live since June 2026. Adopted by three Singapore studios, spread by word of mouth, no marketing.
The product went live in June 2026. It is used not only by the studio it was created for but by others that adopted it since, three Singapore studios in total.
For them it is a tool that adapts to the environment of a studio and the people in it, rather than one they have to work around. Live at inkwell-landing.pages.dev.
A product I designed, built and shipped alone, with real users, and ready to be taken to more studios.
Contact
Open to design leadership roles.
I’m based in Singapore and can work in Singapore and the EU without sponsorship. Available now.