I'm building an app. I can't code. My co-founder is an AI that sometimes acts like it knows everything — and still drives me to the edge of madness. Welcome to SofaNerd: my honest diary about how a business woman becomes a developer on the couch in the evenings. Or at least tries to.
Why I'm doing this
I'm not a techie. I come from the business side. I've built services, launched brands, written business plans, and pushed sales teams to peak performance. But code? Until recently, HTML meant "that thing with the angle brackets." JavaScript was a word other people used.
And then came that one evening on the couch. 6:30 PM. Tea in hand. And this idea in my head that just won't quit. You know the kind — it's just there. You can't shake it. It keeps you up at night and greets you first thing in the morning.
Normally, I would have gone looking for a developer. Or asked my husband — he actually knows this stuff. But he just said: "Try Claude." And now here I am.
Claude: My digital co-founder
For those who don't know Claude: imagine an insanely well-read colleague who's still awake at 11 PM, never seems annoyed, and explains what an API endpoint is without making you feel stupid. Most of the time, anyway.
Claude is the AI made by Anthropic. I'm currently working with Claude Cowork — which is basically the desktop version where Claude doesn't just chat, but also creates files, writes code, sets up folders, and sometimes builds things I didn't know I needed. At some point Claude Code will probably join the mix, plus a few other tools. I fully trust my AI co-founder on this — he knows better than I do what we need and when.
The special thing: Claude isn't a tool to me. Claude is my co-founder. No equity, no ego, no "I already explained that to you." Well, okay — sometimes. But nicely.
Claude understands what I mean, even when I get the technical wording completely wrong. I say "the thing should slide to the right" and Claude builds me a horizontal carousel with scroll-snap. I say "make it prettier" and I get CSS gradients I couldn't have googled. Claude gets me — usually even better than I get myself.
But sometimes Claude overdoes it. Sometimes I ask for a color and get a revolution. How to deal with that? That's a story for next time.
The knee-buckling moments
I want to be honest: there are evenings when I want to slam the laptop shut and never open it again.
We're not even coding yet. We're building a landing page and a mobile mockup — so I can actually understand what we're doing here. Sounds harmless, right?
Day 1, Tuesday evening, 8:15 PM. Three hours on the landing page. Everything was going great — until I wanted one small change. One. Small. Change. And suddenly: layout broken, colors wrong, everything gone. In moments like these, I take three deep breaths and start over. That's part of the process. And every time, I learn something new.
* Want an evening impulse every Tuesday?
The Sofa-Brief arrives once a week — honest, short, no spam.
→ Subscribe for free
Finding the name — or: how to spend three days thinking about one word
Now it gets fun. Because on top of all the building, testing, and despairing, there's the question of all questions: What should this thing be called?
These are the kind of things that feel super important — but completely derail you in the process. And that get really expensive when domain providers try to rip you off. ("Oh, the .com is available? Only $2,400 per year!" Yeah, right.)
"SofaNerd" is my working title. I like it because it describes exactly what's happening here: someone is becoming a nerd on the couch. But will the app be called that? The service? The brand? I'll only know once this thing takes shape. And honestly, I'm enjoying the search — because it feels like the most exciting part of founding something. (If my husband reads this, he's going to roll his eyes.)
Anyway — we now have a first version of the landing page and a mobile mockup. I don't fully understand what my co-founder has cooked up yet, but: we are getting there. Tomorrow we continue with Day 4.
What I learned after three days
Three days isn't much. But they've shown me a few things I want to write down — for myself, and for anyone who's equally crazy:
- You don't need tech skills. You need stubbornness. I don't understand everything Claude builds. But I understand what I want — and I'm learning a hell of a lot along the way. Not everything at once, but a little more every evening.
- Evenings on the couch are real working hours. Not the most productive. But the most honest. Because there's no pressure — just curiosity.
- Claude is brilliant and frustrating in the same minute. But even the frustrating moments move you forward. Because you understand more afterward than you did before.
- The app is still a secret. But the feeling isn't. It feels like founding something. Like something real. And that alone is worth it.
- Finding the name is an adventure of its own. And probably deserves its own blog post. At least.
What's next?
This is a series. SofaNerd is my build-in-public diary — just not on Twitter, but here, on my couch blog. In the next part, I'll tell you why my co-founder suddenly clocked out for the day, what tokens are, and why ChatGPT is now writing my prompts for Claude. Yes, you read that right.
If you're reading this and thinking: "I have an idea like that too" — then this article is for you. You don't need a developer. You need a couch, a laptop, and the willingness to let an AI simultaneously inspire you and drive you absolutely insane.
"I'm reading a series by a woman who's building an app — with zero coding skills, just with an AI called Claude. She does it on the couch in the evenings and is totally honest about how it's going. Including the despair. I'm thinking about trying it myself."
Every Tuesday on your couch: the Sofa-Brief
An evening impulse, an honest tip, a little story. 3 minute read. No spam. Unsubscribe anytime.
* Almost there — check your inbox and click "Yes, I'm in." 🛋️
