The workflow determines the effort
A small internal tool and a platform for several user groups are different projects. The actual workflows matter: who uses the system, what data is processed and which decisions or approvals need support? A useful estimate therefore starts with requirements.
What an estimate needs to include
Beyond visible screens, development includes data models, permissions, validation and integration. Failures, concurrent work and incomplete data also require attention. Testing, documentation, introduction and operation belong in a complete proposal.
Keep the first version focused
A useful first stage covers one important workflow from beginning to end. For example: record an enquiry, assign it, process it and document completion. Extra reports or integrations can follow. Each stage should have clear value and testable acceptance criteria.
Fixed price or time-based billing
A fixed price suits a clearly defined scope. Where requirements are still being discovered or may change, time-based work with a budget limit can fit better. Both approaches need clear rules for additional requests and regular communication.
Consider existing systems
An existing application does not always need replacement. An interface or additional tool may be enough. Access, data quality and technical options must be checked. A controlled test import can reveal the actual work early.
From requirements to a proposal
Describe the current workflow, the people involved and the desired result. Everyday examples are particularly useful. In the initial conversation, we decide whether a workshop, a specification or a bounded implementation is the right next step.
Would you like to discuss your specific needs? Let’s talk about it.