What will we receive?

You receive current-state findings, prioritized product requirements, supporting evidence and a measurement plan. We agree the required page/function maps, acceptance criteria and SRS detail at kickoff, including whether Arabic and English versions are needed. A phased roadmap is included when selected.

What determines the timeline?

We set the schedule after reviewing workflow complexity, available documentation, and stakeholder availability. Review rounds and dependencies are agreed before work starts.

What do you need from our team?

Share your business goals, current workflows, relevant data, and known constraints. We also need access to people who own the processes and approve requirements.

Does this suit an early-stage product?

Yes. We focus on the decision you face now, essential requirements, and assumptions that need testing before you commit to a larger build.

Product Discovery

Turn a product idea into buildable scope. We map workflows, prioritize requirements, and define clear acceptance criteria.

Why?

Unclear requirements create conflicting priorities. We connect each proposed change to a business need, supporting evidence, and an owner so product and technical teams can make informed trade-offs.

Priorities with a reason

See which requirements matter most and the evidence behind their ranking.
Risks before commitment

Surface dependencies and feasibility questions before committing delivery resources.
Measures tied to goals

Define each KPI, its data source, and who will review it.
A shared working reference

Give business, design, and engineering teams one reviewed set of requirements.
A scoped next release

Identify what belongs in the next phase and what should wait for more evidence.

Our process

Agree the decision

We agree on business goals, scope, decision owners, and the measures that will define success.
Map current workflows

We review documents and stakeholder input to map current workflows, roles and constraints, then outline the agreed product pages, functions and key user paths.
Check external context

We use relevant market and competitor evidence to challenge assumptions, noting where deeper research is needed.
Prioritize requirements

We compare value, effort, dependencies, and uncertainty to separate essential requirements from later options.
Build the delivery roadmap

We translate priorities into phases, owners, acceptance criteria, and planning assumptions for effort and resources.
Review and hand over

We walk through representative user paths with your team, check priority requirements against acceptance criteria, record unresolved decisions, and hand over the agreed specification and next steps.