CODEXLABS / PROJECT BRIEF

Start with what matters.
What do you want to build?

Help us understand your challenge. We will organise your answers into a clear document: why the product is needed, what the first release includes and what constraints apply.

No technical vocabulary needed. Describe the task in your own words. Required questions are marked *. Skip the rest or write “I need a recommendation”.

This is a discussion brief, not a final specification or a contract. Answers are kept only in this open tab: save a PDF before closing it.

Project & starting point

Tell us what you do and where you need help. A working title is enough.

Project / company name

What do you need to build?

Current project stage

What already exists

Website, business context, existing materials and what is not working. Share view-only links.

Problem & outcome

Help us understand why the product is needed before discussing screens and technology.

What does the product do and what problem does it solve? *

Main business goal *

How will we know it worked?

A metric or observable outcome. If you have no numbers yet, describe the change you expect.

Users & key journey

Describe the people, their context and their main action in the product.

Who are we building for? *

Customers, employees, partners? Who uses it, who pays, and are there different roles?

Main user journey

Countries, languages & devices

Expected number of users

Roughly per month at launch. “Not sure yet” is fine.

First release & constraints

Separate essentials from what can wait. This helps us estimate a realistic scope.

What must work at launch? *

3–7 features, one per line. Describe actions in plain language.

What can wait or is out of scope?

What services should it connect to?

For example, a CRM, payments, maps, Telegram or inventory. Mention available documentation. Do not share passwords or API keys.

Technical & operational constraints

If known: data migration, offline use, data storage requirements or existing infrastructure. You can skip this.

Design & materials

Let’s establish the visual direction and who prepares the content.

Examples you like or dislike

2–3 links with a note on each: structure, functionality or visual style.

Brand, content & existing assets

Do you have a logo, colours, copy, photos and translations? What will you supply and what should we create?

Timeline & budget

These are discussion starting points, not a fixed price or a delivery commitment.

When would you like to launch, and why?

First-release budget range, USD

If trade-offs are needed, what matters most?

Working together & after launch

Clarify responsibilities, approvals and support early.

Who is involved and who approves decisions?

Team roles, the person coordinating feedback and availability for discussions.

What will you need after launch?

Anything else we should know?

Risks, internal approvals, open questions or preferences.

Contact for follow-up

No contact is needed to preview or download. To send to the company, add your name and one way to reach you.

Your name & role

Email, phone or Telegram

Nothing is sent at this step. Review your answers and edit them before sending.