How We Work Together
Pick the way of working that suits your project. We start from your requirements, then agree everything in writing before we begin.
- Start here
Discovery Sprint
Agreed before we start
1–2 weeks · Fixed fee
A short engagement that turns an idea or a problem into a clear, buildable plan — before you commit to a full build.
Best for: New products, stalled projects, and any build where nobody can yet say confidently what it involves.
- Stakeholder and user interviews
- Workflow and systems mapping
- Technical architecture recommendation
- Prioritised scope split into releases
- Clickable prototype of the core flows
- A delivery roadmap you own outright
Fixed-Scope Build
Agreed in writing, then fixed
4–16 weeks · Milestone-billed
One defined system, delivered to an agreed scope and date, billed against milestones rather than hours.
Best for: A defined product, platform, or module where the requirements are clear enough to commit to.
- Agreed scope, milestones, and delivery dates
- Working software in staging from the first sprint
- A demo and written update every two weeks
- Automated tests and CI/CD pipeline
- Deployment, monitoring, and handover documentation
- 30 days of post-launch support included
Dedicated Team
Reserved capacity, agreed monthly
3 months minimum · Monthly retainer
Embedded engineering capacity that works inside your process, your board, and your standups — for as long as you need it.
Best for: Ongoing product development, or extending an in-house team without a hiring cycle.
- Agreed capacity reserved each month
- Your tools, your board, your ceremonies
- Overlap with your working hours agreed up front
- Direct access to the engineers doing the work
- Monthly reporting on delivery and spend
- 30 days' notice to scale up, down, or stop
Care & Support Retainer
Rolling monthly, cancel any time
Rolling monthly · Monthly retainer
Ongoing maintenance for software already in production — monitoring, patching, and a defined allocation for small changes.
Best for: Live systems that need a named team on call, whether or not we originally built them.
- Agreed response times for incidents
- Uptime and error monitoring with alerting
- Monthly dependency and security patching
- A set allocation of change requests each month
- Quarterly health and technical debt review
- Rolling monthly — cancel any time
How we work with you
We work from your requirements
No two builds carry the same complexity, so we do not publish figures that would fit neither of them. We start by understanding what you actually need, then agree everything in writing before work begins.
We do not bill by the hour
Hourly billing rewards slow work. Discovery and builds are agreed as a whole against milestones; ongoing work is a defined monthly capacity.
You own everything
The code, the data, the infrastructure, the designs, and the documentation are yours from day one — including the right to take them elsewhere.
No surprise invoices
Anything outside the agreed scope is discussed and approved before work starts on it. Nothing lands on an invoice that you have not already agreed to.
Talking to us is free
Tell us what you are building and we will come back with a recommended way to work together — usually within one business day, with no obligation attached.
What every engagement includes, in writing
These are not upsells. They apply whichever model you pick.
You own everything
Code, data, infrastructure, designs, and documentation are yours from day one — including the right to take them to another team.
Direct access to engineers
You talk to the people writing the code. There is no account-management layer between you and the work.
Agreed scope, agreed changes
Scope is agreed once and then fixed. Anything outside it is discussed and approved before work starts — never discovered on an invoice.
Tested before it ships
Automated tests and CI quality gates are part of the build, not an upsell. Nothing reaches your users without passing them first.
Your data stays where agreed
Data handling, access, and residency are agreed in writing before the build. We sign NDAs as standard and no client data leaves the agreed boundary.
Documented handover
Every engagement ends with documentation, architecture notes, and a runbook — so your team can operate the system independently.
Ready to talk it through?
Tell us what you need and we will come back with a recommendation and everything agreed in writing. The first call is thirty minutes and there is no pitch attached to it.
Certified engineering, not claimed
Our AI engineering work is backed by credentials issued by the model vendor itself, not a self-assessment.
Claude Code in Action
Issued by Anthropic · June 2026
Introduction to Model Context Protocol
Issued by Anthropic · June 2026
Introduction to Agent Skills
Issued by Anthropic · June 2026
Scope, Billing & Monthly Retainers
How work is scoped and agreed, how we bill, who owns the result, and how soon we can start
How do you work out what a project involves?
It depends entirely on your requirements, and we would rather tell you that honestly than publish something that fits nobody. A small integration and a multi-team platform are not the same job. So we start by understanding what you actually need, then agree everything in writing before any work starts. Send us a short brief and we will come back with a recommended way to work together, usually within one business day, with no obligation.
How does Develune bill — hourly or per project?
We do not bill by the hour. Discovery is a fixed fee, builds are billed against agreed milestones, and ongoing work is a monthly retainer for a defined capacity. Anything outside the agreed scope is discussed and approved before work starts, so nothing appears on an invoice that you have not already agreed to.
Who owns the code Develune writes?
You do, from day one. The code, the data, the infrastructure, the designs, and the documentation are yours — including the right to take them to another team. Every engagement ends with a documented handover so your system can be operated and extended without us.
How quickly can Develune start?
A Discovery Sprint can usually begin within one to two weeks of an agreed scope. Larger builds and dedicated-team engagements depend on current capacity, which we will tell you honestly on the first call rather than promising a date we cannot hold.
How do we get started with Develune?
Send a short note through the contact page describing what you are building and what is in your way. We will reply with suggested next steps and a recommended way to work together — usually within one business day. The first conversation is 30 minutes and there is no pitch attached to it.