From idea to platform: what to decide before building a digital product

You have spent years doing good work, and your customers trust you. Now you see a new opportunity: a customer portal, an app or a platform to sell your expertise. The idea is clear. Where to start, and who to trust with it, is not.

This is common in established companies opening a new line of business without neglecting the one that pays the bills. The good news: the decisions that matter most are not technical. They are business decisions, and you can make them before speaking to a single developer.

Who it is for and what problem it solves

The first decision is who will use the platform and which specific problem it solves for them. Not “small businesses” or “our customers”, but someone you can picture. Imagine a 50-person health and safety consultancy that wants to sell training online. “Online training” is not a product yet. “The HR manager at a client company signs up their staff, who take the mandatory course on their phones, then downloads the certificates without calling us” is.

Write it down in one sentence. If it does not fit, there is still thinking to do, and doing it now is far cheaper than halfway through the project.

What the first version needs, and what can wait

The first version should include only what a real customer needs to use it and pay you for it. It is not a mock-up: it works, takes payment and solves the problem, just with fewer options than you imagine. If a supplier mentions an “MVP”, this is what they mean: the smallest version that is genuinely useful.

To decide what goes in, ask one question about each feature: without this, can the first customer still use it and pay? If yes, it can wait. In the training example, sign-up, the course, payment and the certificate go in. Advanced reports, other languages and the link to your invoicing software can wait; at first, a spreadsheet will do.

The most common mistake is trying to launch everything at once. Every feature you add pushes back the day you learn something real from your customers.

What sits behind what you see

Behind the screens your customer sees there are payments, user accounts, an admin panel, security, hosting and support, and this hidden part is the most underestimated. When you ask for a quote, check it is all covered:

• Payments: card or direct debit, refunds, invoices and reconciling it all with the bank.
• User accounts: sign-up, forgotten passwords and who can see what.
• Admin panel: the private area where your team manages customers, content and orders without calling a developer.
• Security and data protection: handling personal data properly and meeting rules such as GDPR, the EU data protection law.
• Hosting: where the platform “lives”, the backups, and what happens if it goes down.
• Support and maintenance: who helps the customer who cannot log in, and who keeps the system up to date.

If a quote only talks about design and screens, it is incomplete.

How to test it with the customers you already have

Test the idea with your current customers before you build: ask how they solve the problem today and ask for a commitment, not an opinion. You have something a start-up does not: people who already trust you. Ask a handful what they do now and how long it takes, not whether they like your idea; most people say yes to be polite.

Then show them a prototype, simply a clickable drawing of the main screens, and ask for something concrete: a pre-sale, a reservation or a place in a pilot group. If nobody commits, it is better to know now.

You can even test without technology. Selling the first course by email, taking payment by bank transfer and sending certificates by hand is awkward, but it shows whether there is demand before you invest.

How to choose who builds it

Choose someone who asks about your business before talking about technology. It could be a freelancer, an agency, your own hires or a studio; any of them can work, as long as whoever builds it also answers for the hidden parts and for what happens after launch. Good signs:

• They explain things without jargon.
• They suggest cutting the first version down rather than adding to it.
• They talk about maintenance and support, not just delivery.
• They make clear from the start whose name the domain, the accounts and the code will be in.

Be wary of anyone who gives you a fixed price for the whole product after a single meeting. They do not yet know what they are building.

Budget and timeline: think in phases

Plan the budget in phases, each with a clear goal and a decision at the end:

1. Definition and testing: agree what goes into the first version and check it with customers.
2. First version: build it and launch it with a small group of real customers.
3. Improve and open up: fix what real use has taught you and open it to everyone.
4. Growth: automate, connect it to your other systems and add what was left out.

This way you do not bet everything on one number: at each step you decide whether to continue, change course or stop. Keep money aside for after launch: hosting, fees and support do not go away. And with timelines, fix the date and adjust what goes in, not the other way round.

What you can do this week:

• Write down in one sentence who it is for and what problem it solves.
• Call three customers and ask how they deal with that problem today.
• Split your ideas into “essential to charge the first customer” and “can wait”.
• Decide who on your team will lead the project, and free up their time.
• Note how much you are willing to invest just to find out whether the idea works.

How we approach it at vitamina.dev

At vitamina.dev we start with the business, not the technology. First we help you pin down who the platform is for and what the first version must include. Then we design and build the whole thing: web, app, payments and everything behind them, starting with a version that already works with real customers and growing it in phases.

Our team has built complete platforms in areas such as finance, legal and e-commerce, so we know the hidden part well. And if the conclusion is that it is not yet time to build, we will tell you.

Frequently asked questions

How much does it cost to build a digital platform for my business?

It depends mainly on what goes into the first version and on the pieces behind it, such as payments or connections to your existing systems. So asking up front for a price for “the whole platform” makes little sense. Ask for a quote in phases, and add the running costs: hosting, payment fees and maintenance.

Should I start with a website or an app?

In most cases, start with a website that works well on phones. It is easier to launch and change, and customers do not have to install anything. An app makes sense when people will use it every day or it needs phone features such as notifications or the camera.

Do I need my own tech team to launch a digital product?

At the start, usually not. You do need someone in your company who knows the customers, can make decisions and has real time for the project. An external partner can do the building; if the product grows, you can consider an in-house team once you know which roles you need.