How we work, from first message to long-term partnership

Engagement models

We work in three ways. Most clients start with one and combine them over time.

• Project delivery: a defined scope delivered end to end by a dedicated team, with milestones, a demo every sprint and a structured handover.
• Dedicated team: engineers who join your roadmap for the long term, working inside your processes and tools, scaled up or down as priorities change.
• Technical consulting: short, focused engagements such as an architecture review, a code audit, technical due diligence or help with one hard problem.

From first message to kickoff

An engineer reads your message and replies within one business day. We then hold a short call to understand goals, constraints and the existing technical landscape. For larger projects, a paid discovery phase (usually one to two weeks) turns open questions into a plan before anyone commits to a full budget.

Every proposal is written and specific. It contains:

• the scope, and what is explicitly out of scope;
• the technical approach and the main architectural choices, with their trade-offs;
• the team, by role and seniority;
• milestones, deliverables and acceptance criteria;
• the estimate, the assumptions behind it and the main risks;
• commercial terms: pricing model, payment schedule and validity of the offer.

Delivery rhythm

We deliver in short iterations, usually two weeks. You see working software at a demo at the end of each one, and receive a short written update every week: what was done, what is next, and any risk or decision that needs you.

We work in your tools when you have them (repositories, issue tracker, chat) or set up ours, and every client has a named technical lead as a single point of contact.

Ownership of code and IP

You own the source code, designs, documentation and infrastructure definitions we produce for you, from the first commit and subject to payment of the related invoices. Wherever possible, repositories and cloud accounts are created in your name from day one, so there is never a hand-over of control to negotiate.

We don't use proprietary frameworks that lock you in. Open-source components are listed with their licences, and you receive everything needed to run, change or move the system without us.

Pricing and payment terms

Well-defined scopes are offered at a fixed price; evolving products are billed on a time-and-materials basis with a monthly cap you control. Discovery and audits are fixed-price.

Fixed-price projects are usually invoiced in milestones, starting with a deposit at kickoff. Time-and-materials work is invoiced monthly. Invoices are issued by Sprint Codes LLC in US dollars or euros, payable by bank transfer within the period set in the proposal. The exact terms are always written into each proposal before any work starts.

Typical timelines

Every project is different, but as an order of magnitude: an audit or architecture review takes one to three weeks, a discovery phase one to two weeks, a first production version of a focused product two to four months, and a larger platform is delivered in phases over several months. The proposal always states the plan and the assumptions behind it.

After launch

Software needs care after release. We offer ongoing maintenance and evolution (security updates, monitoring, fixes and new features) under a monthly agreement, or a structured handover to your own team with documentation, runbooks and knowledge-transfer sessions. Either way, the choice stays yours.