How it works
From an idea to an outcome, with a person at every turn.
Six stages carry every project. Agents do the heavy lifting in each one; people set the direction and approve what moves forward.
The journey
Six stages, one written thread.
Each stage leaves something written that the next one builds on, so nothing depends on memory.
-
01Idea
Start with what you need
Open a project and describe the need in your own words, in Arabic or English. Attach the files that explain it.
- You
- Describe the goal, the people it serves and the limits.
- Agents
- Ask clarifying questions and note what is missing.
- What it leaves
- A project with its conversation and files.
-
02Understanding
Turn the need into a shared understanding
The business agent drafts the analysis: users and roles, modules, journeys, data and rules.
- You
- Choose between proposed wordings; nothing you own changes without your choice.
- Agents
- Draft the analysis and propose test scenarios.
- What it leaves
- An analysis and requirements you approved.
-
03Planning
Agree on the plan before anything is built
The architect proposes the data model, screens, routes and API contract. The work is split into phases, or into epics and stories.
- You
- Approve the plan or send it back.
- Agents
- Write the architecture and break the work down.
- What it leaves
- An approved plan.
-
04Work
Build inside the project
Frontend and backend agents work in the project’s own application, one approved phase or story at a time. The live preview shows every change.
- You
- Follow the preview and give feedback.
- Agents
- Build, explain the change and run focused checks.
- What it leaves
- A working application, change by change.
-
05Review
Prove that it works
Scenarios become automated tests, the interface is tested in a browser and performance is reviewed. A code review checks quality and security when you ask for it.
- You
- Read the results and decide what to fix.
- Agents
- Run tests, review performance and report findings.
- What it leaves
- Test results and written findings.
-
06Outcome
Decide to launch
The go-live reviewer compares the result with the analysis and writes a readiness report. Going live stays a separate, approved step.
- You
- Approve the go-live, or send it back.
- Agents
- Check readiness against the analysis.
- What it leaves
- A readiness report and your decision.
Who decides
People decide. Agents assist.
Agents carry the effort of drafting, building and checking. Judgement, approval and ownership stay with people.
People
- Set the goal and the priorities
- Choose between proposed changes to the documents they own
- Approve plans, phases, epics and the go-live
- Decide who can see and change each project
Agents
- Draft the analysis, plans and test scenarios
- Build inside the project’s own application
- Run tests and write reviews
- Explain what they changed and what is still open
Approvals and gates
Built-in moments where the work waits for you.
Gates are part of the platform, not a habit to remember.
-
Plan approval
Every task starts with a written plan that you approve or reject.
-
Phase gate
In phase mode, the next phase opens only when you click Approve & continue.
-
Epic approval and story lock
In story mode you approve the epic first. An approved story is frozen; changes go into a follow-up story.
-
Documents you own
The business analysis and the test scenarios change only after you pick the proposed edit.
-
Access review
Moving a project to another space or folder shows who gains or loses access before you confirm.
-
Go-live
Launching is a separate step that needs explicit approval for a named site.
Questions
Common questions
Short answers to what people ask most before they start.
No. You describe the need, review the analysis and the plan, and follow the live preview. Build tools and the code view are there for developer roles when a team wants them.
No. Agents propose changes to the business analysis and the test scenarios as options, and write only what you choose.
No. Internal and direct projects start straight away. The Business Center is an optional path for teams that deliver to clients.
People whose role allows it, such as the project owner or an administrator. Contributors can work on projects shared with them but cannot approve gates.
Arabic and English. The interface supports a right-to-left layout and light and dark themes.
Estimate calculators and proposal drafts exist in the Business Center and are still being completed, so we label them as in progress.
Request one from the sign-up page. New accounts are activated after an administrator approves them.
A new horizon for your work starts with one step.
Request an account and tell us what you want to build. An administrator reviews new accounts before the first sign-in.
New accounts are activated after an administrator approves them.