Answers before you start.
Can't find what you need? Email us or add the question to your project brief — we reply within one business day.
Getting started
What do I need to get started?
A short description of what you want to build and why. Designs, specs or examples help but are not required — the discovery call and scoping phase are there to fill the gaps.
How quickly will you reply?
Within one business day of receiving your brief, with either questions or a proposed time for a call.
Do you sign NDAs?
Yes. Tick the NDA box on the project form and we will send ours, or sign yours, before you share any details.
Do you work with non-technical founders?
Often. We explain trade-offs in plain language, recommend a sensible stack, and make decisions with you rather than for you.
Pricing & contracts
How much does a project cost?
It depends on scope, so we don't quote blind. After a discovery call you receive a written proposal with a fixed price per milestone or a monthly team rate. The budget range on the project form helps us propose something realistic.
Which engagement model should I choose?
A fixed-scope project suits a well-defined build with a clear finish line. A dedicated team suits ongoing product work where priorities shift. A support retainer suits a live product. We recommend one after the first call.
What happens if the scope changes?
Change is normal. On fixed-scope projects each change request is priced before work starts and you approve it in writing; with a dedicated team you simply reprioritise the backlog.
Who owns the code?
You do. The code sits in your repository from day one, and the contract assigns all intellectual property to you.
Delivery
How do you keep us updated?
A weekly check-in, a demo every two weeks, a shared chat channel and access to the project board. You never have to chase us for a status update.
Can we see the work before launch?
Yes. Every sprint is deployed to a staging environment you can use, so your feedback is on real software, not screenshots.
Can you work with our in-house developers?
Yes. We can join your repository, follow your conventions and review process, and pair with your team so the handover is smooth.
After launch
Do you provide support after launch?
Every project includes a 30-day warranty covering bugs in our work. After that you can move to a monthly support retainer or take the product in-house.
Can you take over an existing codebase?
Yes. We start with a code and infrastructure audit, then give you a written report of the risks and a plan before making any changes.
Will we be locked in to Sendixa?
No. You own the code, the cloud accounts and the documentation, so another team can take over at any point.
Still have a question? Email sendixa.info@gmail.com or send a project brief.
Have a project in mind?
Tell us what you want to build. We reply within one business day with questions or a time for a call.