06 / Before we begin
Practical questions.
A clearer starting point.
You can bring a specification, an existing application, or a business
problem that still needs definition.
Should we build custom software or use an existing platform? +
Start with your workflow, constraints and the products already available. We can assess where configuration or an extension may fit, and where a custom application is needed. The recommendation depends on that assessment.
Can we start with an existing application? +
Yes. Share the current system, available documentation, integrations and the changes you need. Access and a technical assessment help establish what can be reused, what needs attention and how to scope the next step.
Can the project include web, mobile and integrations? +
The scope can include these together or separately. Devices, user roles, existing APIs and data dependencies help determine the application boundaries and delivery effort.
What changes the estimated effort? +
The number and complexity of workflows, roles, interfaces, integrations and data migration all matter. Quality requirements, deployment environments and handover also contribute. The Project Effort Estimator gives an initial manhour breakdown to discuss with the team.
What happens after launch? +
Release guidance, documentation and handover are agreed as part of the delivery scope. Stabilization, ongoing maintenance and new features are discussed according to the support your team needs.
What should we bring to the first conversation? +
A business objective, the people who will use the software, a description of the current workflow, and any known systems or constraints. An existing specification or prototype is useful, but you can also begin with a problem that needs clarification.