How we work
A process you can see working.
Five stages, weekly working demos and no black boxes. Here is how a project runs at OlDevs, from the first strategy call to the growth work after launch.
Weekly working demos You own everything Reply within one business day
Availability - November
Live312
Bookings this month
1.8%
No-show rate after optimisation
How we work, in short
OlDevs runs every engagement through five stages: a strategy call to discover goals and constraints, design, build with a working demo every week, launch, and grow.Clients choose from three engagement models (Project, Retainer or Product partner), own all code, designs, accounts and IP from day one, and receive builds that meet WCAG 2.2 AA in English and French. Work is quoted on scope, with quotes returned within one business day.
Key facts
- 01Stages
- Discover, Design, Build, Launch, Grow
- 02Demo cadence
- A working demo every week
- 03Ownership
- All code, designs, accounts and IP are yours
- 04Accessibility
- WCAG 2.2 AA
- 05Languages
- English and French
- 06Quotes
- Returned within one business day
Process
Five steps, one accountable team.
Discover
It starts with a strategy call. We learn what you are trying to achieve, who will use the product, what already exists and what has to be true at launch. Then we scope it honestly. Deliverables: Written brief, scope and quote, proposed timeline and team
Design
Wireframes first, then visual design and a clickable prototype you can put in front of real users. Accessibility, bilingual layouts and performance are designed in, not bolted on. Deliverables: Clickable prototype, design system, content plan, WCAG 2.2 AA checklist
Build
Engineering runs in weekly cycles. Every week you get a working demo on a staging environment, not a status slide, so feedback lands while it is still cheap to act on. Deliverables: Weekly working demo, staging environment, automated tests, code in your repository
Launch
QA, performance and accessibility audits, a security review, then a planned release with monitoring in place. Handover means your team can run it without us. Deliverables: Launch checklist, documentation, training session, account and code handover
Grow
A launch is a starting point. We measure what people do, fix what gets in their way and, if you want, run the marketing that puts the product in front of more of them. Deliverables: Analytics setup, monthly performance report, prioritised roadmap, support agreement
By the numbers
Where the effort goes in a typical build.
Most of an engagement is building and growing — the phases you can see.
Strategy call, scope, success metrics
Flows, interface, design system
Engineering, weekly working demos
Hardening, docs, handover
Marketing and iteration after launch
Illustrative shares of a typical fixed-scope build — every engagement is scoped individually.
Engagement models
Scoped around your goals, not a fixed menu.
Every engagement is quoted individually. Tell us what you need and we reply within one business day.
Project
A defined scope, a fixed team, a launch date.
The right fit when you know what you need built: a website, an app, a portal or an AI feature with a clear finish line. We scope it, quote it and deliver it in weekly demos.
Organisations with a specific product or campaign to launch.
- Discovery and written scope
- Design, build, QA and launch
- Weekly working demos
- Documentation and handover
- Post-launch warranty period
Retainer
Ongoing capacity for a product that keeps evolving.
A standing allocation of design, engineering or marketing time each month. Priorities shift as your business does, and the team already knows your codebase and your customers.
Teams with a live product, a marketing programme or a backlog that never quite empties.
- Reserved monthly capacity
- Shared backlog and sprint planning
- Ongoing SEO, paid media or lifecycle programmes
- Monitoring, maintenance and updates
- Monthly reporting and roadmap review
Product partner
Your technology team, end to end.
For founders and organisations that need a whole product built and grown without hiring a department. We handle strategy, design, engineering, AI and marketing as one team, and you own every asset.
Startups and organisations launching a new digital product or line of business.
- Product strategy and roadmap
- Full design and engineering team
- AI and data capability as needed
- Go-to-market and performance marketing
- Quarterly planning with your leadership
What to expect
How an engagement feels from the inside.
Cadence
Weekly cycles with a planning call at the start and a working demo at the end. Larger programmes add a monthly review with your leadership.
Communication
A named project lead, a shared channel your team can join, and written updates you can forward. No question waits more than a business day.
Demos
Every demo runs on a real staging environment. You click through it yourself, and your feedback goes straight into the next week's plan.
Ownership
Repositories, design files, hosting, ad and analytics accounts are opened in your name. If we part ways, everything already belongs to you.
Documentation
Architecture notes, setup guides and runbooks are written as we build, so your team, or any future vendor, can pick the work up.
Support
A post-launch warranty on every project, then support and maintenance on terms that suit you, from ad-hoc fixes to a full retainer.
Technology
Proven tools, chosen for your team — not ours.
We pick the stack your people can run after launch. Every platform has its own page in the Technology section.
Web
Mobile
Back-end & cloud
AI & data
Marketing & analytics
Design & QA
FAQ
Questions about working together.
It depends on scope, but as a guide: a marketing website usually runs a few weeks, a web or mobile app a few months, and a full-stack system or AI product longer. The Discover stage ends with a timeline you can plan around.
No. Your project lead translates between business goals and engineering decisions, and weekly demos let you judge progress by using the product rather than reading about it.
It usually does, a little. Small changes are absorbed within the weekly cycle. Larger ones get a written impact note covering time and cost, and nothing changes until you approve it.
You do, from day one. Code lives in your repository, designs in your Figma workspace, and every hosting, ad and analytics account is registered to your organisation.
Yes. We start with a technical audit covering code quality, security, performance and accessibility, then recommend whether to stabilise, refactor or rebuild, with a quote for each path.
WCAG 2.2 AA is the standard for every build, checked in design and verified in QA. Bilingual English and French delivery covers interface copy, content and metadata, not only a translated page.
Insights
More on how we work.
Longer pieces on the decisions behind the process.
Web security and privacy in 2026: what changed and what to do now
Passwords gave way to passkeys, privacy law arrived in force, accessibility got deadlines and AI added new risks. What changed through 2026 and the checklist to…
Performance marketing that proves itself: attribution basics for non-marketers
Attribution decides which marketing gets credit for a sale. No model is perfect; the aim is a fair, consistent method that shows where budget actually works.
What an AI copilot actually costs to run in production — and how to keep it reliable
Model fees are the smaller share of a copilot's running cost. Tokens, latency, monitoring and guardrails are the larger one, and they decide whether it stays…
Let’s connect
Ready to start?
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote.