Our Service
Our Service
How Aliensync is engaged, what each stage includes, and what you get at the end. Every engagement starts with a written scope and a fixed quote, so you know the number before any work begins.
Engagement models
Three ways to work with us
Pick the one that matches the shape of the problem. We will tell you if you have picked the wrong one.
Project build
A defined piece of work with a start, an end and a fixed quote.
- Written scope before work starts
- Fixed price against that scope
- Staged delivery you can see
- Full handover at the end
Ongoing partner
A continuing relationship for products that keep evolving.
- Agreed monthly capacity
- A team that already knows your system
- Planned roadmap work
- Priority on urgent issues
Review and advice
An independent look at something that already exists.
- Codebase or architecture review
- Cloud cost and security audit
- Written findings and priorities
- No obligation to have us do the work
Pricing is quoted against your scope rather than published as a list, because a one-line figure for “a social platform” would be meaningless. What is fixed is the process: you see the number, in writing, before anything starts.
Process
What happens, step by step
First conversation
You describe the problem and the constraint, whether that is a date, a budget or an existing system. We ask questions. Nothing is charged for this.
Written scope and quote
A document setting out what will be built, what is explicitly excluded, the stages, the timeline and the price. You take as long as you want with it.
Design and architecture
Data model, interfaces and infrastructure agreed before building, because these are the decisions that are expensive to undo.
Build in stages
Each stage lands somewhere you can open and use. You see progress continuously rather than at the end.
Testing and review
Functional testing, load testing where it matters, and a round of your feedback before launch rather than after it.
Launch and handover
Deployment, monitoring, documentation, runbook and credentials. Support afterwards is optional and separately agreed.
Commitments
What we commit to
- A fixed number against a fixed scope. Scope changes are re-quoted, not absorbed quietly and billed later.
- One point of contact who knows your project, rather than a different person each week.
- Code you own from the first commit, in a repository under your control.
- An honest no. If the thing you are asking for is better solved by an off-the-shelf tool, we will say so.
- Plain answers about risk. Including when we are not sure.

Questions
Service questions
How much does a project cost?
It depends on scope, and a figure quoted before seeing yours would be a guess. What we can promise is that you get a written number against a written scope before you commit to anything, and that the number does not move unless the scope does.
How quickly can you start?
That depends on current capacity. We will tell you a real date rather than an optimistic one, because a project that starts late after being promised early is worse than one that started honestly.
What if we are not happy with a stage?
Each stage is reviewed before the next begins, which is the point of staging the work. Problems surface while they are still cheap to fix.
Can we stop part way?
Yes. Work completed is handed over at the stage reached. You are not locked into finishing something that stopped making sense.
Do you work with clients outside your own country?
Yes. The work is remote by default, with meetings scheduled to overlap your working hours.
Next step
Ready for a scope?
Describe what you are trying to build or fix. You will get questions first, then a written scope and a number. Neither commits you to anything.
