Pricing and project estimates.

Start with the outcome

We scope software and workflow projects around the outcome, existing tools, integrations, delivery requirements and operating responsibility.

Two ways to work together

With managed care, the build fee is negotiable and the monthly price is firm for the agreed coverage. New features and third-party usage are separate unless expressly included.

With delivery and handover, you or your partner maintain the result. The project fee covers the agreed development, testing, documentation, handover and defect obligations. Future maintenance income is not assumed and a queue position does not determine your price.

Ask for an estimate

Tell Ask bwebo the desired outcome, current tools and integrations, what is essential, timing, and whether you want us to maintain the system or hand it over. The assistant can clarify scope and prepare an indicative estimate using the current quotation policy. Missing requirements or unconfigured rates are identified instead of invented. Effort ranges are assumptions to check, not promised delivery times.

An estimate identifies its currency, policy version, validity, inclusions and exclusions. It is subject to scope and written acceptance, and does not reserve a delivery slot, accept a contract or initiate payment. Care, third-party subscriptions/usage and applicable taxes must be clear before acceptance. An introductory pilot reduction, if agreed, is limited to that scope.

We assess suitable opportunities across industries. Existing software, a smaller useful scope or targeted help may fit better than a new custom application. Enquiries remain private; public queue summaries need separate permission and review.

Pricing is reviewed annually and sooner when costs, support or alternatives change. A new policy does not automatically change an accepted engagement. Discuss a project.