MVP and startup product development
An MVP is the first working version of a product, limited to the features needed to launch and learn. Eltemur Zentra Studio scopes that version, builds it, and stays available after it is in use.
Who it is for
- A founder with a clear problem and no working product yet.
- A startup that needs to test payment, signup, or the core task with real people.
- A team that wants a smaller first release instead of a long build.
Problems it solves
The idea is larger than the first release
The first version should prove one workflow. Scoutier launched around outreach from the user’s own mail app. Shopidict launched around one store audit.
There is no way to learn from use
A clickable picture is not enough when the question is whether people will sign up, pay, or finish the task. The first version has to be usable.
Payment is left until later, then blocks the launch
If the test includes a paid step, Paystack can be part of the first version. That is how Scoutier, Shopidict, UIPrep, and Passcarda charge.
What Eltemur Zentra Studio can build
- Product discovery: the user, the problem, and the first workflow.
- Feature prioritisation so the first release stays small enough to ship.
- A prototype or first release people can actually use.
- Authentication when the product needs accounts.
- Payment integration with Paystack when the first version charges.
- A simple admin path when someone must update content or review records.
- Testing of the main path, then deployment.
- Post-launch fixes and the next agreed slice of work.
Main deliverables
- A short scope that says what the first version includes and what it leaves out.
- The working product for that scope.
- Accounts and payment only when the test needs them.
- A deployed version a real user can open.
- A follow-up path for fixes after launch.
How this work runs
01 Discovery
We write the problem, the user, and the single outcome the first version must produce.
02 Planning and design
We cut the feature list to what that outcome needs, then map those screens.
03 Development and testing
We build the first version and test the path from arrival to the outcome, including payment if it is in scope.
04 Launch and support
We help put it in front of users and use what happens next to decide the following slice of work.
Technologies on related work
React, TypeScript, Vite, Supabase, Paystack, Flutter, Dart, Tailwind CSS
First versions already shipped use this set where it matched the product: React and Supabase for web products, Paystack when they charge, and Flutter for the offline Android app GradeNG.
Related work
- Scoutier
Personalized email outreach for the web, Windows, and Android. People find public addresses, clean a list, personalize the message, and send it from their own mail app.
- Shopidict
An online store audit tool. It reviews a store and shows a score, the revenue impact, and the most important issue.
- UIPrep
A practice product for University of Ibadan Post-UTME past questions, including explanations, Roman Series questions, and mock exams.
- GradeNG
An offline Android app for calculating CGPA under Nigerian university and polytechnic grading systems.
- Passcarda
A web app for practising JAMB and post-UTME past questions, with explanations and timed mock exams.
Questions
What does a first version usually include?
The task a user must complete, and only the accounts, payment, or admin tools that task requires. Eltemur Zentra Studio does not publish a fixed feature list or a fixed price for every startup.
Can you launch a paid product in the first version?
Yes, when payment is part of the test. Scoutier, Shopidict, UIPrep, and Passcarda use Paystack. The amount charged is a decision for that product.
Do you stay after launch?
Yes. Launch is followed by fixes and the next set of improvements that the use of the product justifies.
Start a project
Tell Eltemur Zentra Studio what you want to build, who it is for, and where you want to start.
Start a Project