For design, marketing & digital agencies
You lead the client.
We build the agreed work.
Bring us the website, application or integration your client needs. Add a technical owner and people to build it.
Your designs.
A working website.
Illustrative roles. Your agreement defines the actual scope and responsibilities.
- 01 / Your agency
Bring the design.
Approved layouts, content and a client decision-maker.
- 02 / Modern Labyrinth
Build. Test. Review.
A working preview, responsive layouts and agreed checks.
- 03 / Agreed approver
Accept, then launch.
Release approval, source files and operating notes.
Agree scope, fee, access and release authority before work. Client communication, brand visibility and ongoing support are agreed with you.
Scope, roles and working arrangements
- 01
The client relationship
Your agency & client
Lead the relationship, priorities and commercial conversation.
Modern Labyrinth
Work through the communication route you agree with us.
Agree before this step Client contact, brand visibility and escalation owner.
- 02
The work to take on
Your agency & client
Bring the brief, approved designs or the problem to solve.
Modern Labyrinth
Clarify feasibility, dependencies, implementation scope and exclusions.
Agree before this step A written scope, commercial terms and a named technical owner.
- 03
Build and review
Your agency & client
Coordinate client inputs and identify who can resolve open questions.
Modern Labyrinth
Implement the agreed work and provide a reviewable version with check results.
Agree before this step Review environments, access, feedback route and acceptance checks.
- 04
Acceptance and release
Your agency & client
Name the person who accepts the work and the person who may authorize release.
Modern Labyrinth
Prepare the agreed handoff and release only when authorized to do so.
Agree before this step Acceptance evidence, release authority, recovery plan and support boundary.
Other work we can scope
Applications, API integrations, database and SQL work, commerce workflows and websites. Technical leadership can cover architecture and delivery decisions; it does not automatically include a development team.
Behind-the-brand delivery, client discussions and handoff to your developers are different arrangements. We agree who supplies content, owns accounts and supports the result.
See examples of a scoped project →AI-assisted work, accountable delivery
Claude and Codex support implementation and review. A technical owner is responsible for decisions and checks. We agree client-data access, tool permissions and the evidence needed to accept the work.
Bring the brief
Where does your team
need a partner?
Describe the client project, what already exists and the part you want us to build. Tell us who reviews the work.
We clarify scope and what the work depends on before proposing a team, price or schedule.