Deliver more websites with the team you have.
Discovery, design, build, QA and launch, run the same way for every project. Your team keeps the calls on scope and launch. Your agents do the checking, sorting and first drafts.
An example of how a web studio could set this up. Nothing here is a built-in template.
Your team
Sets up the QA pass
Your agent
Checks pages, outside ORCA
Project lead
Decides what blocks launch
Your client
Confirms the launch date
Finding. One issue blocks launch. The rest can be fixed after go-live.
Recommendation. Fix the form before launch and schedule the rest for the first week after.
Every project runs the same stages. Every client signs off on its own.
Define the website project once: discovery, design, build, QA, launch. Who prepares each stage, who reviews it, what the client signs off. Each project runs it with its own brief, files and decisions.
Nothing here is built in. Click an owner to change it, click a step to rename it, add one.
Delegate the QA pass. Keep the call on launch.
Hand the page-by-page check to an agent that already has your browser testing tools. Scope it to one campaign. Your project lead decides what blocks launch and what the client sees.
- Agents run on your setup. ORCA holds the task and the context.
- A role, a permission list and a campaign boundary. The server checks every request against them.
- Review points live in the workflow. Approval is a workflow step owned by the reviewer. Approve campaign output is off for the agent.
- Contact form fails validation on mobile
- 12 pages missing meta descriptions
- Hero images uncompressed on 4 templates
Illustrative. Your agent runs on your own setup. Sharing stays off until the reviewer approves.
Clients confirm the launch. They never see the bug list.
The client gets the QA summary, what will be fixed before launch, and one decision to make. The full findings, who ran the check, and your project lead's edits stay on your side. Try the switches in the workspace.
Never shown to the client: workflow controls, owner assignment, agent permissions and scope. Hidden until you switch them on: who prepared the work, internal review notes.
Common questions.
Short answers about how a web studio would run work in ORCA.
Does ORCA host staging sites or run the tests?
No. Your team or your agent tests the site with the tools you already use. ORCA holds the task, the briefs, the QA report and the review step, and shows the client what you choose to share.
Can the client sign off on discovery and designs the same way?
Yes. The workflow you define can end each stage with a shared deliverable and one client decision: approve the sitemap, approve the designs, confirm the launch. You set the stages and the review points.
Who decides what the client sees?
Your studio. By default the client sees the QA summary, the recommended launch plan and the decision you need. The full findings, internal edits and agent details stay with your team.
Same product. Same review step. A different service each time.
Pick the one closest to yours and see the workflow, the assignment and the client view shaped for that kind of work.
Start with one project. Build from there.
Run the QA pass for one build with your team, refine it, then hand the page checks to an agent when you are ready.