How it works
The process is designed to reduce uncertainty. Scope is clarified before any build starts, the work stays visible while it is in progress, and the handover is structured so ownership is practical afterwards.
The core process
Conversation
We start with what is not working, what you want to improve, and whether Studio Dali is the right fit. No heavy prep needed.
Clarity before build
Before any build starts, we agree what is being made, what is not, what success looks like, and what the project needs from you.
Build and refine
The work moves in short cycles so you can see progress, give feedback, and keep the project aligned with the real goal.
Handover and support
You get a clean handover, practical guidance, and optional follow-on support if you want it after launch.
What happens before build starts
The project only moves into build once the scope is clear enough to make the work calm, focused, and measurable.
Clarify the problem
What is not working, what should improve, and which part of the business needs the most attention first.
Set the working scope
What is included, what is deliberately not included, and what a good outcome should look like when the project lands.
Confirm the practical inputs
Anything needed from you before the work starts, such as existing copy, access, examples, or decisions that unblock the build.
What clients usually need to provide
A rough description of the current problem or friction.
Any existing website, workflow, or software context worth reviewing.
Access to relevant accounts or tools if the project needs them.
Timely feedback on agreed checkpoints so the build can keep moving.
Typical timeline examples
Exact timings depend on scope, but the rough shape below helps set expectations before the work starts.
Focused landing page
Often measured in days rather than weeks when scope and content are already clear.
Strategic business website
Usually a few weeks once the page structure, messaging, and review rhythm are agreed.
Workflow or tool build
Varies more because logic, testing, and edge cases matter as much as the interface.
What handover includes
The aim is not just to finish the project. It is to leave you with something you can understand, use, and keep running.
A clear explanation of what has been built and how it works.
Access and ownership arranged under the right accounts where relevant.
Notes on anything that needs ongoing attention after launch.
Practical guidance on where to ask for support or what to update yourself.
Support after launch
Some clients want a clean handover and independence. Others want light ongoing support. Both are fine.
Independent handover
Best when you want to own the setup fully and manage the next steps yourself with clear guidance.
Ongoing support
Useful when you want occasional refinements, fixes, or follow-on work without rebuilding the whole relationship from scratch.