Cut it in half, then ship it
The features every client asks for in v1, and why we usually talk you out of three of them.
· 4 MIN READ
Almost every scoping conversation starts the same way: a list of everything the product could eventually do, presented as everything it needs on day one. Our job in that first week isn't to say yes to all of it — it's to work out which of those features the launch actually depends on, and which ones are safe to add after real users show up. Four requests come up often enough that we can talk about them by name.
Multi-language, before there's a second market
Bahasa Malaysia, English and Mandarin support is genuinely useful — for a business that already has customers in more than one language today. Building it into the structure from day one costs little. Translating every screen before a single user has clicked through the first one is effort spent on a problem you don't have yet.
AI features, without a use for them yet
Smart search, summaries and suggested replies are easy to get excited about and hard to justify without a specific job for them to do. The honest question is what decision or task gets faster because of it. If there's a clear answer, it stays in. If the answer is "it would be nice," it waits for v2, once real usage shows where it would actually help.
Loyalty and rewards, before there's traffic to reward
Points, tiers and referral programs only work once there's a customer base large enough to make the mechanics worth running. Launching with a loyalty system and no customers is building the second floor before the ground floor has a roof.
Reporting and exports, beyond what anyone will read
Dashboards and exports are useful right up until they're a wishlist of every chart someone might theoretically want. We'd rather ship the two or three numbers the business actually checks every week, and add the rest once we know which ones get used.
The one that usually stays
The feature that survives this conversation is almost always the one tied directly to the reason the project exists — the booking flow for a booking app, the checkout for a store, the wallet for a loyalty platform. Everything else is a fair question for v2, once the core is live and there's real usage to design around instead of a guess.
If you're not sure which of your own list is core and which is a nice-to-have, that's exactly what a one-week scope is for. Shape it on the homepage and we'll tell you honestly which half to cut.
Not sure what your v1 actually needs?
Shape it on the homepage in about twenty seconds, or send us three sentences and we'll tell you.