FAQ
The questions settled before signing
These questions run longer and deeper than the ones on the service pages, because they are the ones that recur at the contracting stage rather than while browsing. If yours is not here, send it on WhatsApp and you get a direct answer with no sales call.
Cost and contracting
Pricing and payment
Why is there no pricing published on the site?
Because the gap between a brochure site and a full ERP is enormous, and any published figure would mislead one side or the other. We send a written cost once we understand the scope.
How is the cost calculated?
From the agreed scope: the number of pages or modules, the integrations required, and the volume of content. We itemise it in the plan rather than giving one total.
What are the usual payment stages?
Payments tied to delivery stages rather than to dates. You pay as each stage is approved, which protects both sides and keeps progress visible and measurable.
Are there monthly costs after handover?
Hosting and the domain only, and both are in your name directly. We charge no subscription on the code and no licence fee, and support beyond the agreed period is a separate arrangement.
Delivery
Timelines and how work runs
How long do projects usually take?
A brochure site takes weeks. A store or news portal takes longer. A custom system depends on its modules and integrations. The dates go into the written plan.
What if we are late reviewing a stage?
We flag the schedule impact immediately rather than discovering it at the end. We agree a reasonable review window per stage at the start.
How many revisions are included?
Revisions within scope are included, and each design stage carries two review rounds. Anything outside scope is estimated in time and cost before it starts, and you decide.
Who do we deal with during the project?
The people doing the work, not an account management layer. Day-to-day contact is on WhatsApp or email, and decisions that matter get documented in writing.
Ownership and support
After launch
Who owns the code and the designs?
You do, entirely and without restriction, from the moment of delivery. We hand over the repository, design files and operational documentation, and any other team can continue.
Can we change developer later?
Yes, with no technical or contractual obstacle. We build with widely used technologies and document deployment and operation specifically so moving on is not expensive for you.
What does post-launch support cover?
Fixing faults that surface after go-live, within the agreed period. New development and additional features are estimated as separate scope.
Can you work with our technical team?
Yes, and it usually helps. We agree the split of responsibilities and code standards at the start and hand over in a way your team can pick up.
What if we end the engagement midway?
You receive everything completed and pay only for the stages delivered. That is written into the contract and needs no negotiation later.
Start here
Tell us about your project
Send us two lines about what you need on WhatsApp. We reply, book a short scoping call, then send a written plan with cost and timeline before you commit to anything.