FAQ
Questions buyers ask before the first call
Short, direct answers. If yours isn't here, ask us: an engineer replies within one business day.
01
Getting started
How do we start?
Send a few lines about your project through the contact page. An engineer replies within one business day, we hold a short call, and you receive a written proposal.
Will you sign an NDA before we share details?
Yes. We sign a mutual NDA before you share anything sensitive, on your template or ours.
How long does it take to receive a proposal?
Usually within a week of the first call for a clearly defined project. Larger or less defined projects often start with a short, paid discovery phase that produces the plan and the estimate.
Do you work with startups as well as established companies?
Yes. We adapt the engagement to the stage of the company, from a first product version to the evolution of an existing platform.
02
Contracts and payment
Fixed price or time and materials?
Both. Well-defined scopes are offered at a fixed price; evolving products are billed on time and materials with a monthly cap you control. See how we work for details.
How do payments work?
Fixed-price projects are usually invoiced in milestones, starting with a deposit at kickoff; time-and-materials work is invoiced monthly. The exact schedule is written into each proposal.
Which currencies do you invoice in?
Invoices are issued by Sprint Codes LLC in US dollars or euros and are payable by bank transfer.
Who owns the code?
You do. You own the code, designs and documentation we produce for you, subject to payment of the related invoices, and repositories are created in your accounts wherever possible.
03
Working together
Can you work in our time zone?
We work remotely with clients in different time zones and agree on daily overlap hours for live discussion, complemented by written updates.
Which languages do you work in?
English, French and Arabic, for meetings, documentation and written updates.
How will we follow progress?
You get a demo of working software at the end of each iteration, a written update every week and direct access to the engineers through a named technical lead.
04
After launch and existing code
Do you maintain software after launch?
Yes. We offer monthly maintenance and evolution agreements, or a structured handover to your team with documentation and runbooks.
Can you take over an existing codebase?
Yes. We start with an audit of the code, infrastructure and delivery process, then propose a plan that stabilises the system before adding new features.
What happens if we want to end the engagement?
You keep everything we built. We hand over code, documentation and credentials, revoke our access and confirm it in writing. Notice periods are set in the contract.