What a first product version should include

Include the task, and leave the rest out

The first version should let one kind of user finish one job. Scoutier’s job is personalised outreach from the person’s own mail app. Shopidict’s job is one store audit that returns a score, the revenue impact, and the main issue. GradeNG’s job is an offline CGPA record.

Features that do not serve that job can wait. A first version that tries to include every later idea takes longer and teaches less.

Add accounts only when the person must return

If the product stores a list, a score history, or a paid plan, it needs an account. Scoutier, Shopidict, UIPrep, and Passcarda use accounts. A simple public website does not need one.

Supabase is the database used on those web products. It is a fit when the product needs users and saved data, not a default for every page.

Add payment when the test includes getting paid

If the question is whether people will pay, the first version should be able to take payment. The products that charge use Paystack. This site does not publish a standard price, because the amount depends on the product.

If the first question is only whether people understand the offer, a website and an enquiry path are enough. Do not add billing to answer that question.

Keep an admin path small

Someone on the business side may need to update content or see a record. The Mayus Alaro site has an admin panel for that. Put it in the first version only when launching without it would block the product.

• Write the user and the job in one sentence.
• List the screens that job needs.
• Add accounts, payment, or admin only if the job fails without them.
• Ship that version, then decide the next slice from real use.