Comprehensive field guide
The Custom Software Field Guide
This field guide brings the main custom Software Development decisions into one place: how to read the symptoms, protect the current state, choose a scope, compare paths, and verify an outcome that matters to businesses needing internal platforms, portals, dashboards, and specialized applications.
Read the situation before naming the solution
Begin with critical operations rely on disconnected tools, who experiences it, and what changed before it appeared. Distinguish the visible symptom from the system boundary that may involve web application architecture and delivery.
- Critical operations rely on disconnected tools
- Staff re-enter the same information repeatedly
- Existing software cannot match the workflow
Protect the current state
Confirm ownership, access, backups, and a recovery path before changing production. Preserve exact errors and timestamps because they may disappear after a restart or update.
- Access owner
- Current backup
- Restore method
- Change history
Define the smallest useful result
Frame the first scope around internal management and workflow systems and one observable acceptance journey. Keep dashboards, reports, and searchable databases as a later phase unless it is a true dependency.
- Internal management and workflow systems
- Customer and partner portals
- Dashboards, reports, and searchable databases
Compare repair, extension, and replacement
Repair fits when the core remains sound; extension fits when the boundary is understood; replacement fits when ownership, architecture, or operating risk prevents responsible change.
- Time to value
- Data risk
- Reversibility
- Maintenance ownership
Plan implementation and launch
Sequence work around relational databases and secure data models, protect users affected by reporting requires manual spreadsheet assembly, and define the point at which rollback is safer than continuing.
- Relational databases and secure data models
- Role-based access and administrative tools
- APIs, webhooks and third-party integrations
Verify and hand off
Repeat the original journey, test a nearby failure, document the result, and make responsibility explicit. A successful handoff leaves businesses needing internal platforms, portals, dashboards, and specialized applications able to understand what changed and what happens next.
- Acceptance evidence
- Current documentation
- Monitoring owner
- Prioritized next step