Our process
Clear steps, no surprises.
Every project is different, but the rhythm stays the same: understand, agree, design, build, verify and support. Here is what working with Vidana OU looks like.
Timeline
Eight phases from idea to impact
Introductory conversation
A short call or email exchange to understand what you want to achieve, any constraints and how you prefer to work. There is no obligation at this stage.
→ Shared understanding of the goal
Discovery
We dig into users, existing systems, content and success criteria. For larger projects this can be a small paid phase of its own.
→ Written brief and scope
Proposal & agreement
You receive a proposal describing deliverables, approach, timeline, responsibilities and cost. Work begins only once it is agreed in writing.
→ Signed agreement
Design & prototyping
Wireframes, visual designs or playable prototypes — depending on the service — so you can react to something concrete.
→ Approved direction
Iterative build
Work proceeds in short cycles with regular previews. Feedback is gathered continuously and priorities can be adjusted.
→ Working product
Quality assurance
Functional testing, device and browser checks, accessibility review and performance tuning before anything goes live.
→ Release candidate
Launch
Planned deployment with backups and a rollback path, followed by close monitoring in the first days.
→ Live product
Support & evolution
Optional ongoing care: updates, fixes, monitoring and new features as your needs grow.
→ Continued improvement
Communication
You will have a single point of contact, regular progress updates and access to preview environments throughout the build.
Your involvement
We ask for timely feedback at key checkpoints and access to the information and content only you can provide.
Change requests
Ideas evolve. New requests are discussed openly, with their impact on time and cost made clear before any change is accepted.
Tools & artefacts
What you receive along the way
Written brief
A short document capturing goals, audiences, constraints and success criteria.
Proposal
Deliverables, timeline, responsibilities and cost, agreed before any build work.
Designs or prototypes
Wireframes, visual designs or playable builds to review and refine.
Preview environment
A private link where you can see and test progress at any time.
Test summary
An overview of what was tested, on which devices and with what results.
Handover documentation
Access details, usage notes and technical documentation for the future.
Principles
Why we work this way
Most problems in digital projects come from misunderstandings, not from code. A structured process reduces those misunderstandings by making decisions visible and written down.
Short iterations mean issues are found early, when they are cheap to fix. Regular previews mean you never wait weeks to see results. And a clear launch and support plan means the product keeps working after the project ends.
Ready for step one?
The introductory conversation costs nothing. Tell us about your project.