How we think.
Notes from building things: what worked, what didn’t, and what we’d do again. If you read one, you should come away with at least one thing you can use.
-
What running an EdTech platform at scale taught us about building one
Lessons from running the engineering behind a one-to-one tutoring platform serving twenty-plus countries: the schedule is the product, the live class must always work, and parents want to see, not ask.
edtech · operations · lessons
-
Marketplace MVP: which side to build first, and what to leave out
A two-sided marketplace is three products pretending to be one. How to choose the first side, scope the first transaction, and avoid the operations trap.
marketplaces · mvp · product development
-
An MVP in 60 to 90 days: a realistic plan, week by week
What a first version actually looks like from the inside: what happens in foundations, what the build weeks contain, what gets cut, and what you have at the end.
mvp · product development · guide
-
Where AI helps in a business, and where it just adds noise
A plain map of the places AI genuinely saves time in a small or mid-sized business, the places it does not, and how to tell the difference before spending money.
ai · operations · guide
-
What you should own at the end of a software project
Code, accounts, data, documentation, and the ability to leave. A checklist for anyone paying a studio to build software, and why being easy to leave is how we keep partners.
ownership · handover · partnerships
-
How to brief a software studio and get a useful estimate back
You do not need a specification to start a software project. You need the problem, the people, and honest answers to six questions. Here they are.
guide · partnerships · product development
-
What to automate first: a ranking method for small teams
Automation pays back fastest when you start in the right place. A simple way to rank the candidates, and the three automations that come first for almost everyone.
automation · operations · guide
-
Digitising a business that runs on WhatsApp and spreadsheets: where to start
Most businesses already have a system. It is made of chat groups, sheets and one person's memory. Here is how to turn it into software without stopping the business.
digitisation · operations · whatsapp · guide
-
Shipping fast without breaking things: Our pragmatic approach to quality
How we move fast and maintain quality without heavy testing overhead. A practical approach to building software that works.
development · workflow · quality · pragmatism
-
Choosing a software development partner: 10 questions to ask
How to choose the right software development partner for your project. Questions to ask, red flags to watch for, and what makes a good partnership.
business · partnerships · software development · guide
-
Product foundations: What to build in your first 60-90 days
A practical guide to building product foundations. How to narrow your idea, define scope, choose your tech stack, and ship something meaningful quickly.
product development · mvp · guide · foundations
-
AI-assisted development: How we use AI without replacing judgment
How Zofwe uses AI to enhance software development while keeping humans in charge. Practical examples of AI-assisted workflows and when to use AI vs. when not to.
ai · development · workflow · technology
-
Building software with clarity and craft
Why we started Zofwe and how we build calm, thoughtful software with humans and AI.
philosophy · craft · culture · humans-and-ai
Have something
worth building?
Tell us what it is, in a few lines. We'll say honestly whether we're the right people for it, and what a small first step would look like. No decks, no discovery-call theatre.
Zofwe · Product studio · Kerala, India · Working with teams anywhere