Custom business systems

Start with the work, not a feature list

A spreadsheet can be the right tool for a small, flexible task. Difficulties arise when several people need to update related records, control access, follow approvals or reconcile conflicting versions. The problem is often the workflow around the spreadsheet rather than the spreadsheet itself.

A custom business system brings records and actions together. A customer record can connect to orders, registrations or outstanding tasks. A staff member can see the information needed for a particular responsibility. Reports can draw from the same operational records rather than a separately maintained summary.

When a custom system makes sense

Custom software is worth considering when a distinctive workflow is central to the business, the data relationships are specialised, or existing tools create substantial repeated work. The case for building should include the effort of ownership: support, access management, backups, upgrades and changes to the business process.

If an established product already fits the requirement, configuring it may be more practical. If a process is still changing every week, simplifying it first may be more useful than automating it. The discovery work should make that choice clearer.

Handle exceptions as carefully as the normal path

Operational software needs to account for corrections, cancellations, incomplete records and changes of responsibility. Access rules must match what people are allowed to view and change. A report needs a clear definition of which records it includes.

These decisions are easier to assess with a focused release and representative examples. The school operations case study shows how scheduling, registration, attendance, credits and reporting were brought into the same operating environment.

Problems we can help with

• The same information is copied between spreadsheets and messages.
• Approvals depend on chasing people and reconstructing a decision history.
• Staff cannot see a consistent view of customers, orders or daily operations.

What we can build

• Customer and member records with relationships to operational activity.
• Quotation, order and approval workflows.
• Staff portals, role-based access and operational dashboards.
• Specialised databases, reporting and administrative tools.

How we work

• Map the current workflow, records, exceptions and responsibilities.
• Compare a custom solution with improving existing tools or adopting a suitable product.
• Agree a focused first release and test it against realistic operational scenarios.
• Plan migration, training, support and subsequent improvements.