Topic
MVP
Technical insights from FlareTech about MVP.
- Architecture14 min read
When to split a frontend monolith — and when you should not
A frontend monolith is one app you deploy as one. Split only when cadence, ownership or blast radius are actually two jobs — not because microfrontends sounds grown-up.
→When to split a frontend monolith — and when you should not - Method12 min read
What to put in a web RFP — so you can compare bids
An honest RFP says what must be true at launch, what you already have, and what is out. A 200-line wish list is not something you can compare.
→What to put in a web RFP — so you can compare bids - Web12 min read
When a design system pays off — and when it is a folder
A design system is a contract about tokens, ownership, and not inventing the button again. A component library without those three things is a folder.
→When a design system pays off — and when it is a folder - SaaS11 min read
Transactional email that arrives: DNS, templates and ownership
If the reset mail hits spam, it is rarely the template. It is DNS, the sender, and who owns the domain.
→Transactional email that arrives: DNS, templates and ownership - Method12 min read
Feature flags for a small team — without the platform theatre
A feature flag is a runtime decision. Not a dashboard subscription, and not an env var you forget to turn off.
→Feature flags for a small team — without the platform theatre - Method12 min read
How to run an honest discovery week
A discovery week is five days that replace the requirements spec nobody can estimate from — with decisions you can actually build.
→How to run an honest discovery week - Architecture11 min read
When to replace a legacy system — and when not to
A system should be replaced when it blocks the business — not because it is old. Here is how we separate modernisation, wrapping and the expensive rewrite.
→When to replace a legacy system — and when not to - AI12 min read
AI chatbot for customer service: when does it actually make sense?
An AI chatbot for customer service makes sense when most contacts are repeatable and you have sources to answer from. It does not make sense as a substitute for a messy process.
→AI chatbot for customer service: when does it actually make sense? - Method11 min read
How to choose a web agency — ten questions before the contract
You choose a web agency by testing whether the partner understands business goals, scope, ownership and operations — before any code is written.
→How to choose a web agency — ten questions before the contract - SaaS5 min read
Stripe, billing, and org auth — what to have in place before your first paying customer
Billing and auth are the first place a SaaS product becomes expensive to fix afterwards. Here is how we think about Stripe, organisations, and self-service together — without reinventing what Stripe has already solved.
→Stripe, billing, and org auth — what to have in place before your first paying customer - AI6 min read
When does RAG make sense — and when is it the wrong AI project?
RAG has become the default answer to "we want to use our own data with AI". It's often right — and expensively wrong when the real problem is search, process, or data quality. Here's the honest sorting.
→When does RAG make sense — and when is it the wrong AI project? - SaaS5 min read
Multi-tenant architecture: when, how — and what can wait
Multi-tenant sounds like something you must decide on day one. In practice it's a scale of choices — from "everyone in the same database with an org id" to full isolation. Here's how we choose without over-engineering the MVP.
→Multi-tenant architecture: when, how — and what can wait - AI3 min read
AI agents in production — what must be in place before you ship
A demo agent that answers smartly in ChatGPT is not a production agent. Shipping AI to real users requires boundaries, observability, and a clear definition of when a human takes over.
→AI agents in production — what must be in place before you ship - SaaS3 min read
SaaS MVP: what belongs in v1 — and what waits
The hardest part of an MVP isn't building features — it's not building them. v1 should prove someone will use the product, not that you've built a mini enterprise platform.
→SaaS MVP: what belongs in v1 — and what waits - Web7 min read
When does it make sense to hire a Next.js agency?
In-house, freelancer, or a Next.js agency — the choice isn’t about prestige. It’s about pace, ownership, and what happens when the product has to live in production for years.
→When does it make sense to hire a Next.js agency? - Architecture8 min read
When should you choose custom-developed software?
Off-the-shelf gets you very far — until it doesn't. Here's how we think about the threshold between staying on the shelf and building your own, without turning it into a religious conversation.
→When should you choose custom-developed software?