What to prepare before a software project starts

Name the person and the job

Write who will use the product and what they need to finish. “A candidate practises University of Ibadan Post-UTME questions” is a job. “We need an app” is not. Eltemur Zentra Studio starts from that job, then chooses a website, web application, mobile app, or first product version.

Bring examples, not a full specification

A few reference products are useful if you can say what you want to copy and what you do not. A long list of screens is less useful than the path from the first screen to the result.

If you already have a name, a logo, or text you want used, include it. If you do not, the project can still start from the workflow.

Say whether anyone must pay, sign in, or work offline

These three answers change the build. Paid products we have shipped use Paystack. Products with accounts use a database such as Supabase. GradeNG is offline because students need the record without a connection. Say which of those apply, even if you are unsure of the technical approach.

Decide what the first release must prove

State the outcome that would make the first release worth putting in front of someone. It might be an enquiry, a completed audit, a practice score, or a saved CGPA. Work that does not serve that outcome can be listed as later work.

You can send this in the project form, by email, or on WhatsApp. The contact page has all three.