A project should be easy to follow, even when the work is complex.
We agree what needs to change, make the work available to review and keep decisions visible. Here is how a brief becomes a working system, and what happens when the plan needs to change.
Follow a project throughThis sequence describes a build. Discovery can be a separate engagement when requirements need investigation. Dates depend on scope, access and review availability; we agree them in the proposal.
Show us what happens today: a spreadsheet, a repeated task, a customer journey or a system that no longer fits. We ask who is affected, what you have tried and what would make the work worthwhile.
We examine the workflow, data, existing systems and exceptions. If an integration is central to the project, its access and capabilities need checking before the plan depends on it.
The proposal sets out deliverables, exclusions, milestones, responsibilities and acceptance criteria. Subscriptions, content, migration and training need a clear place in that agreement.
We develop in reviewable pieces. Your team checks real tasks: submitting a request, correcting information, rejecting an approval or finding a record. Feedback is tied to the agreed requirements.
We review the agreed acceptance criteria, resolve delivery issues and coordinate deployment. Access, configuration, data movement and responsibilities after launch are checked within the agreed scope.
An issue with agreed functionality and a new feature request are different kinds of work. We establish which applies and whether the next step falls within included fixes or a separate agreement.
A written update every week, even the quiet ones, with a live preview link.
Completed tasks are only part of the picture. We also identify what needs your attention and whether an unresolved decision affects delivery.
Use the preview to try the workflow with your team. Specific feedback such as “the second approver cannot see the attachment” gives us something we can reproduce and resolve.
Any change in scope is written down and priced before we do it. Nothing is added to your bill without your yes.
We first check whether a request corrects an agreed requirement or adds something new. For an addition, the decision includes the work involved, dependencies and any effect on delivery.
You can approve it, keep it for a later release or keep the current scope. The latest agreement should reflect the decision.
These are our standard project commitments. Your signed proposal and the linked terms define the engagement, including its scope and any separately agreed services.
Every project has a fixed price, agreed in writing before we start. The number we quote is the number you pay.
50% to start, 25% when the work is halfway done, and the last 25% before delivery.
Your accounts, domains and code repository are in your name from day one, and the code is yours as you pay for it.
30 days of fixes after launch are included. Training is quoted separately, and ongoing support is on a monthly retainer.
Your application code is yours. If it's built on OmnioPHP, the framework itself stays open source under GPL-3.0, and we'll walk you through what that means.
All prices, quotes and invoices are in US dollars (USD). Read the Terms and Conditions and Refund Policy for acceptance, cancellation and payment provisions.
Search visibility and performance marketing continue beyond a single delivery. The engagement needs an agreed remit, access, budget authority and a review cadence.
A written update every week, even the quiet ones. We distinguish work completed, results observed and the next action. A ranking movement or a new enquiry is evidence to examine, not proof that one change caused it.
You talk to the person doing the work. No account managers.
Based in Kolkata, India. Our working day runs 5:00 to 21:00 IST, and we'll take a call at any hour by arrangement.
No. Start with the task you need to improve and a real example. We can help identify requirements. Where substantial investigation is needed, discovery is scoped separately before committing to the build.
No. It is useful when the workflow or priorities need investigation; a clearly defined project may not need one. A Systems Audit is $1,500 USD, credited in full to the build if you go ahead within 90 days.
Yes, subject to the systems and access involved. We establish who controls each integration, who reviews changes and who owns deployment. An existing supplier or internal team may need to participate in discovery and testing.
Tell us as soon as you can. We identify the affected work and confirm scheduling implications. Dependencies and review responsibilities belong in the project plan; a delivery date cannot be assessed independently of them.
We're happy to sign your NDA before the first call. You can first describe the problem without supplying sensitive records. We then agree what access or sample data is actually needed.
30 days of fixes after launch are included. Training is quoted separately, and ongoing support is on a monthly retainer. We agree documentation and handover requirements in the scope, including what your team needs to operate the delivered system.
A free 30-minute call with the person who would build it. Tell us what is happening today and what you want to make easier.
Start a conversation