Our Journey: Building SWAIN in Public
We built SWAIN in public, one post at a time. A behind-the-scenes look at how we developed, tested and refined SWAIN from scratch. Watch our Journey unfold
Week 1: Getting Started
Honest Conversations and Unexpected Emotions – day 5
As the Mom Test interviews rolled in, the reality of what dev teams were feeling hit us hard. Small agency leaders talked about being squeezed by clients. Cutting corners just to meet deadlines.
Talking to Strangers – day 4
Day 3 marked a turning point for SWAIN as we connected it to a real database for the first time. This is where the idea became working code.
Wiring It Up- day 3
Day 3 marked a turning point for SWAIN as we connected it to a real database for the first time. This is where the idea became working code.
Walking the Talk – day 2
On Day 2 of building SWAIN, we explored how walking and talking helped clarify the real cost of building software. A reflection on time, value and honest direction.
The Journey – day 1
1903: Two brothers stood on a windswept beach, staring at their fragile machine. It had no right to fly. Experts laughed at them. Scientists dismissed them. The press ignored them.
Week 2: First Experiments
From Inspiration to Reality – days 12 to 14
SWAIN’s direction matured through outside feedback, real-world challenges and a shift in mindset. These days solidified the vision we were building toward.
Defining the Product – Days 8 to 10
These three days reshaped our direction. From questioning the value of developer tools to cutting back the MVP, this was where focus truly formed.
Why We Build: Challenging the Status Quo – Day7
For me, it’s always been about challenging the norm. I’ve never accepted that things have to be done the same way just because that’s how it’s always been done. I look for the cracks in the system—the moments where a better approach could exist—and I build from there.
Week 3: Gaining Clarity
Quiet Miles, Clearer Minds – days 16 to 22
On Day 16 of building SWAIN, a quiet walk sparked a major shift in how we saw the product. It’s not about control, it’s about removing burden.
Week 4: The First Real Output
Half a Size Bigger – Day 26
It’s all moving now. The feedback is shaping the story, and the white paper is opening doors.
Snowy Hair and Sharp Insights – Day 25
we hit a feature request that wasn’t planned until phase two. But after talking to some devs, we realised it was a game changer. So it’s now being brought forward.
Not Just Another Builder– day 24
It plays nicely with what you already use. It generates clean APIs, auto-builds models, and handles complex queries — using the database as the source of truth. That’s why it’s not a competitor to Retool, it’s a complement for serious backend work.
Rooted and Relevant – day 23
On Day 23, a calm moment sparked a deep shift in mindset. SWAIN found its voice not through features, but through purpose.
The First Full Loop – day 22
On Day 22, SWAIN generated its first working CRUD API from a real database. This was the moment theory became real.
Week Five: Slower Steps, Sharper Thinking
The Benchmark Drop – day 30
We ran two tests. One API build done the standard way: ORM, model mapping, manual joins — the works. It took over 6 hours.
Welcome to the Chaos – day 29
We’re building SWAIN to be radical, yes — but also frictionless to adopt. For developers, that means no disruption to workflow, and real productivity gains. We tested SWAIN head-to-head against traditional API builds. The time saved was shocking.
Space to Think, Space to See – day 28
On Day 28, a quiet Sunday walk helped bring clarity to the direction of SWAIN. Some progress happens in silence.
Just Keep Walking- Day 27
It’s all moving now. The feedback is shaping the story, and the white paper is opening doors.
Week Six: Resisting Complexity, Choosing Clarity
Simplicity is the Strategy – day 35
On Day 35, the team at SWAIN recommitted to keeping things simple — in process, product, and priorities.
The Magic Button– day 34
If you’ve ever built APIs, you know this pain:
Modelling the data. Mapping the relationships. Writing the endpoints. Testing them. Adjusting. Documenting. Hours lost in boilerplate and backend glue.
Talent, Trust and Teamwork – day 33
Day 33 reminded us that SWAIN is not just a product — it’s a team effort. When trust is strong, progress follows naturally.
Expanding the Circle – day 32
On Day 32, we began inviting others into the journey. SWAIN’s reach widened beyond developers to real-world teams trying to do more with less.
Under the Hood – day 31
What’s really exciting is that this part of SWAIN takes a totally different approach to API generation, drawing on AI principles to help build descriptive, robust interfaces. It’s fast, it’s reliable, and it works with the way developers actually think.
Week Seven: Listening Clearly, Building Sharply
The Eve of Launch – day 41
We’ve shared it all: the wins, the worries, the wrong turns.
Warts and All – day 40
This was a day of honesty and resolve. SWAIN isn’t perfect. But it works. And it works fast.
Slots, Sites, and Systems– day 39
Building in public has kept us sharp. It’s exposed flaws, but also forced clarity. And the team? Absolutely outstanding.
The Home Stretch – day 38
Building in public has kept us sharp. It’s exposed flaws, but also forced clarity. And the team? Absolutely outstanding.
Proving the Value, Publicly and Personally – day 37
Our team moved forward with test-driven development, UI builds, and feedback loops. The energy was infectious.
“Wait… What?” – day 36
People compare it to Postman or Apidog. But it’s not. It’s a whole new category.
We’re confident enough in what we’ve built that we launched an offer:
From Noise to Signal- day 42
On Day 42, the SWAIN team shifted from chasing feedback to interpreting it. The Mom Test brought clarity and next steps.