Tell us what you need built

Who we'll provide updates to. Normally this is you, the person completing the form.

Please enter a name — this is who we'll send updates to.

The role of the person making this request — this is about accountability for the request, not who'll actually use the finished tool (that's the next section). If this is something someone else asked you to get done, put their role here — e.g. if Jonathan asked for this, put "CEO".

Please enter an actual role or job title.

Not you or whoever asked for this — the person who'll actually be the one going through this journey day to day. e.g. "Salon assessor", "Finance administrator", "Store manager".

Please name the actual role of the person using this day to day — not "staff" or "user", and not the requester's own role from Q2 unless they're genuinely the same person doing this.

Picture that person going about their day. What are they trying to do, and how do they currently do it — step by step? This helps the team understand exactly what's being replaced.

A complaint like "too much manual work" describes the problem, not the journey. Walk through the actual steps — e.g. "I receive a file by email each week → I open it → I manually check it against a reference list → I flag anything that doesn't match."

Describe what you want this tool to do for the end user, in a sentence or two — think of it as replacing what you described above with something better. If it's complex, the team will follow up directly.

"I just want an app" doesn't tell the team what the end user would actually experience. Describe the journey in a sentence or two — e.g. "An app where I upload a weekly file and it flags any entries that don't match our expected format."

What's better for the end user once this exists — time saved, fewer mistakes, a faster answer? If there's a specific deadline, explain why here.

Please explain what's actually better for them — not just "because it's needed".

Be specific about the real details involved at each step — not just a general description.

Something like "spreadsheet data" is too broad. Name the actual details — e.g. "location name, staff name, date, category, amount."

e.g. assessing a photo = judgement every time. Storing photos so a person can compare them later = it doesn't.

Please choose one — Yes or No — so we build the right kind of tool.

Please describe or list real examples — not just a description. If you don't have real examples yet, say so here rather than guessing; we'll help you source them before anything is built.

Please give real examples of good/bad cases, or write "Not yet available" — a general description on its own isn't enough.

e.g. pass/fail, a score, written feedback, a downloadable file, or a combination.

Please describe what they actually see or receive, not just a single word like "feedback".

Mention if you expect this to grow.

Please include an approximate number of people and how often it'll be used (e.g. "10 people, ~30 times a week").

Think about who else — your team, customers, salon teams, other departments, franchisees, etc. — might be affected, even if they're not the ones directly using it. A rough sense is fine; if you're not sure of the scale or haven't spoken to anyone yet, just say so.

Just a bit more than a single word — even a rough sense is fine, e.g. "Other teams, not sure yet how much this affects them."

Client, candidate, or employee personal data — names, IDs, contact details, or anything identifying.

Please confirm either way — even a clear "No" is fine, but this can't be left blank or "not sure".

e.g. anyone internally, a specific team, or partners externally.

Please name a specific group or team — if it genuinely is everyone, say that explicitly rather than leaving this vague.