How to brief a React.js developer so the first sprint ships

Most React.js projects stall on an unwritten brief

Hiring a React.js developer with “make it modern” is how you get a component library and no product. The first sprint ships when the brief names users, the job, and the data.

Copy this one-pager

1. Who: role and the device they use (desk vs phone).
2. Job: the one workflow that would make you pay for the screen.
3. Data: where it lives today (API, sheet, nothing yet).
4. Auth: who may see it, and what they must never see.
5. Done: a URL, a real user, and a failure state if the API is slow.

If SEO matters—landing pages, a journal, pricing—you likely want a Next.js developer (React.js plus a frame Google can read). If it is an internal tool behind login, React.js as a SPA can be enough. I wrote the tradeoff in React.js vs Next.js.

Questions I ask in the first call

• Does this screen create money, save time, or only look new?
• Is there already an API, or is the React.js app pretending to be the backend?
• Will a second page copy-paste 400 lines, or is there a boring structure?

A React.js developer who cannot talk about the API is a frontend-only hire. Say if that is what you want.

What I ship

Production React.js UIs, Next.js when the site must rank, and the NestJS / Node path when the domain is heavy. Message faizan.codes with the one-pager above—not a shopping list of libraries.