30% off on MVPs−30% on SPRINT
Valid for another
Places available44/5044 places available out of 50
Black Friday: SPRINT is 30% off until Friday 27 November.Book the call →
Black Friday promo: -30% sui progetti MVP. Prenota la call.
SPRINT on an existing product

A new feature for your software, in 14 days at a fixed price

A new module in production on your existing product, with scope written on day 0 and the price fixed before work begins.

First SPRINT price−30%€15,000, €20,000 or €25,000€10,500, €14,000, €17,500Subsequent features with SPRINT+, €5,000 in 7 days.
sprint.modulo
$ dn3 sprint --repo existing
3 core flows   €15,000
4 core flows   €20,000
5 core flows   €25,000
payment        50% start, 50% release
code           client-owned from first commit
then SPRINT+   €5,000, 7 days
14 daysto the first module in production
€15,000-€25,000first SPRINT, fixed price
€5,000each subsequent feature in 7 days
The problem

Adding a module on an hourly basis means reopening a project without a defined cost.

VariableHourly vendorDN3
PriceHourly estimate, revised for each unexpected issue in the codeFixed price, agreed at the feasibility call
Time to releaseWeeks or months14 days
ScopeDefined as work progressesWritten on day 0
Impact on existing codeChecked at the end of the workAutomated tests and daily review of affected parts
Subsequent featuresA new quote each timeSPRINT+: 7 days, €5,000

The first engagement is a SPRINT: DN3 works in the codebase, releases the module and documents it. From then on, each additional feature has a fixed duration and price.

The process

First a SPRINT, then SPRINT+.

[01]

SPRINT, 14 days. The first module, at €15,000, €20,000 or €25,000 based on core flows. DN3 works in the existing repository and delivers with tests and documentation.

[02]

SPRINT+, 7 days. One additional feature for €5,000, fixed price, paid in advance.

[03]

Requirement. SPRINT+ is available only to clients who have completed a SPRINT with DN3.

How it works

14 days, 5 phases, 3 client approvals.

A pipeline of agents writes the code; a DN3 engineer leads it and is accountable for it. The client brings a one-page brief; on day 14 they receive a product in production that they own.

D0Gate 01

Brief

60-minute feasibility call. Scope is locked in writing.

D1-2Gate 02

Spec

Agents produce PRD, data model, API and flows. The client approves.

D3-10

Build

Parallel agents on a fixed stack. Daily human review.

D11-13Gate 03

QA

Automated tests, load tests and a session with five real users.

D14

Release

Deploy on the client's domain, analytics on, handover of repository and docs.

[01]

Gate 1, D0. Scope locked. Later requests become a new sprint.

[02]

Gate 2, D2. Spec approved by the client. From here the build runs with a daily report.

[03]

Gate 3, D13. The client approves the production release.

What you receive on day 14

The deliverables of a SPRINT on existing code.

  • Module in production on the existing product
  • New code in your repository, with branches and pull requests available for review
  • Automated tests for the module and the existing parts it affects
  • Technical documentation of the module and changes
  • Updated deployment pipeline
  • Testing report with 5 real users
  • Backlog of upcoming features, sized for SPRINT+
  • One hour of recorded handover for the internal team
14/14

The day-14 rule. If on day 14 the product is not in production with the scope locked on day 0, the remaining 50% is not owed* and DN3 completes the work at its own expense. Scope is written and signed by both parties on day 0.

Conditions

* The rule does not apply when the delay is not attributable to DN3: scope-change requests during the sprint, client approvals or answers not delivered within the gate timelines, or outages of third-party services outside DN3's control, including AI service providers, cloud platforms and network infrastructure. In such cases the remaining 50% remains due under the contract terms.

FAQ

Technical questions at the feasibility call.

Yes. DN3 accesses the repository as a collaborator and works on dedicated branches with pull requests. The stack, existing tests and deployment environment are checked at the feasibility call.

Web apps, including ones installable on the phone (PWA), on widely used, documented stacks, such as TypeScript, React, Node.js, Python and PostgreSQL. Compatibility is confirmed at the feasibility call, before the price is fixed.

The client, from the first commit. The code is written in your repository.

Critical parts, such as payments, authentication or sensitive data, are identified on day 0 and covered by dedicated tests, daily review and a release approved by the client at gate 3. If the risk cannot be managed within 14 days, the scope is reduced before work begins.

Feasibility call

Three questions. Then choose a date and time.

The product type is already set to a module on an existing product. The answers help prepare a preliminary scope.

Day and time

Loading availability…

Promo 30-BLACK-FRIDAY: −30% on SPRINT, 44 left. Saved with the booking.

By booking, your details are used only to organise the call and reply to you, as described in the privacy policy.

Reply within 4 business hours. Alternatively, write to hello@dn3.dev.

Book a feasibility call