Why the product backlog is not moving (and what to try first)
Stuck backlogs are usually unclear acceptance, too much WIP, or no one who can say no. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Kiwi Blog 161 articles · Page 5 of 7
The Kiwi Blog.
Practical articles on websites, client portals, SaaS, and technical SEO. Understand the trade-offs before you invest in the build.
Search all articles, or browse by topic below.
Browse by topic All articles
Product velocity without junior hand-offs
Handoffs to juniors look cheap and cost reviews. Senior-only delivery is a staffing choice you should ask for in writing. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Reduce CSS runtime cost without a rewrite
Runtime CSS-in-JS and unused frameworks tax INP. Prefer a tokenized static stylesheet when the UI is known. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Replacing spreadsheets with a workflow without boiling the ocean
Spreadsheets die when permissions, history, and concurrent edits matter. Replace one workflow, not the company. A practical sequence, common mistakes, and what to prepare before you brief a studio.
robots.txt for AI crawlers on a B2B site
Named AI crawlers do not inherit the * group's Disallow. If you want citations, allow them and restate private paths. A practical sequence, common mistakes, and what to prepare before you brief a studio.
The admin panel is how SaaS MVPs slip six weeks
Internal tools expand without a user. If admins can use the database and a script, the panel can wait. A practical sequence, common mistakes, and what to prepare before you brief a studio.
SaaS MVP analytics: the few events that change decisions
Event soup hides the only number that matters: did the user finish the core job? A practical sequence, common mistakes, and what to prepare before you brief a studio.
Auth and roles in a SaaS MVP: what to ship first
Ship the smallest role model that cannot leak data. You can add roles; you cannot casually undo a confused permission model. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Build vs no-code for a SaaS MVP: a decision you can defend
No-code is right for learning. Custom is right when data, access control, or IP must be yours without platform tax. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Cloudflare, a PaaS, or a VM: hosting choices for a SaaS MVP
Hosting is a risk choice: who patches, where data lives, and how you deploy at 11pm. A practical sequence, common mistakes, and what to prepare before you brief a studio.
What actually changes the cost of a SaaS MVP
Cost moves with workflow count, roles, integrations, and compliance review — not with the colour of the buttons. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Questions to ask a SaaS MVP development agency
Agencies look similar until you ask about ownership, environments, tests, and who writes the risky integrations. A practical sequence, common mistakes, and what to prepare before you brief a studio.
What should happen before SaaS MVP development starts
Code is the expensive way to discover the workflow. A short discovery should lock the first-value moment, data model, and out-of-scope list. A practical sequence, common mistakes, and what to prepare before you brief a studio.
How to hand a SaaS MVP to an internal team without a stall
Handoff fails when there is no runbook, no tests, and no one who has deployed it twice. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Integrations that should not delay a SaaS launch
Every integration is an SLA you do not control. Launch with one, mock the rest, and write the failure UI. A practical sequence, common mistakes, and what to prepare before you brief a studio.
A scope-cut list for an overweight SaaS MVP
If everything is v1, nothing ships. Cut by whether a user can complete the job without it. A practical sequence, common mistakes, and what to prepare before you brief a studio.
A security baseline for a first SaaS release
You do not need a certification to avoid the obvious failures: secrets in git, missing access control, and verbose errors. A practical sequence, common mistakes, and what to prepare before you brief a studio.
How much testing is enough for a SaaS MVP
Enough testing is the suite that fails when the core job breaks. Coverage percentages without that are theatre. A practical sequence, common mistakes, and what to prepare before you brief a studio.
SaaS onboarding: design for the first value moment, not the settings tour
Onboarding dies in configuration. Time-to-value is the first time the user completes the core job with sample or real data. A practical sequence, common mistakes, and what to prepare before you brief a studio.
How to define a credible first SaaS release
A first release is one workflow a user can finish. Feature lists are how v1 becomes v4 in disguise. A practical sequence, common mistakes, and what to prepare before you brief a studio.
From waitlist to paid without overbuilding the product
A waitlist teaches demand. Charging teaches willingness to pay. Neither requires your full roadmap. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Service page SEO without thin copies of the same blurb
Six service pages should not share a paragraph with the noun swapped. Each needs a distinct buyer, outcome, and not-for. A practical sequence, common mistakes, and what to prepare before you brief a studio.
What to leave out of your XML sitemap
Sitemaps should list canonical, indexable URLs only. Admin, noindex legal pages, and parameter copies do not belong. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Put analytics consent on the launch site from day one
Shipping analytics 'just for a week' without consent is how you inherit a cleanup. Default off, one loader, ads denied. A practical sequence, common mistakes, and what to prepare before you brief a studio.
Put the thinking to work
A useful read.
An even better next step.
Tell us about your website or product. We’ll help you identify the problem worth solving first, with a clear path to a scoped project.
Start a project