When is custom software worth it?
When an important workflow has requirements that available products cannot reasonably support, or the manual work between tools has become the real system. Compare subscription and integration options first, then the ongoing ownership cost of a custom build.
Compare custom and ready-made software
How do you scope a client portal?
Start with who signs in, what each role may see and the actions they need to complete. Requests, documents, approvals and status updates can then form a focused first release. We agree acceptance checks and test permissions between users and organisations; a login screen alone is not a complete access model.
What affects cost and timing?
Workflow complexity, permissions, data migration, external integrations and approval availability affect both. Existing records may need cleaning before migration. Discovery establishes the dependencies and a written scope before a delivery schedule is agreed.
Understand the scope factors
Who owns the system afterwards?
Handover covers the accounts, custom code, infrastructure and operating guidance in the agreed scope. Third-party products and libraries retain their own licence terms. Ongoing maintenance and support responsibilities should be written down rather than assumed.
See delivery and handover
Can it work with our current records?
We assess the source data, access rights, formats and relationships first. A migration needs a mapping, validation checks, a cutover plan and a recovery option. The same applies when connecting an existing customer, accounting or operational system.