Blog category
Practical notes on planning products, scoping first versions and keeping budgets honest.
AI helped us turn pay rules into code and tests quickly. The hardest parts turned out to be writing the rules down and getting payslips into inboxes.
The number of screens matters less than you think. Here are the things that really move the budget of a first SaaS version, and how to keep them in check.
Most product problems start before any code is written: unclear scope, missing decisions or a budget built on guesses. These posts share what we have learned helping founders and teams plan and build. For step-by-step help, see how to plan a SaaS MVP and our SaaS development services.
Keep exploring
Start a project
Send a short brief. We reply with questions, a suggested plan and an estimate you can compare with other offers.
Loading the search index...
Search is not available right now. Try the HTML sitemap.
No matches. Try a shorter word, or browse the resources.
Type at least two letters. Press / anywhere to open search.
We use necessary storage to run this site. With your permission we also use Google Analytics to see which pages help people, and load maps from Google. You can change this at any time. Read the cookie policy.
Necessary
Remembers your theme and this choice. Always on.
Analytics
Google Analytics 4, to count visits and see which pages help. No advertising.
Maps and embeds
Loads the Google map on the contact page and other outside content.
