Buy well if it exists. Build it if it does not. Know the difference.
Getting your organization the software it actually needs — which means, in order: finding out whether the market already sells it, buying well if it does, and building it if it does not.
Does this sound like your software?
“You run nine to thirteen products that do not share a record, so the same client is entered repeatedly and the same document is requested more than once.
“A supervisor cannot see a single current picture of a case without opening four systems.
“A software purchase was made on a demo, and the product turned out not to fit the regulated workflow it was bought for.
“Enterprise systems are priced for enterprises, small-business tools do not understand regulated program delivery, and what would fit does not exist.
“A previous implementation stalled, because nobody mapped the workflow, cleaned the data, or trained the staff.
How we get you the right system
- Requirements written from your actual workflow and evidence obligations, not from a vendor feature list.
- Market scan and shortlist with a written assessment of fit, three-year total cost of ownership, data portability, and the specific regulated requirements each candidate does and does not meet.
- Structured demonstrations scripted against your own scenarios and scored on a published rubric.
- Contract and security review support — data ownership, export rights, term and renewal, service levels, subprocessors, breach obligations — with legal review by your counsel.
- Implementation management: configuration, data migration and cleanup, integration, user acceptance testing, training, cutover, and a hypercare period.
- A documented recommendation not to buy, where the honest answer is that the workflow needs fixing before any product will help.
How we get you the right system
- Discovery and requirements. Current-state inventory, requirements specification, architecture and security design, tenant foundation, enablement roadmap. Nothing is used in production during this phase.
- Foundation development. Core administration, identity, roles, and the first working modules built and submitted for your written acceptance. Use rights attach only on acceptance.
- Program enablement. Remaining modules built and submitted, each accepted before it carries real work.
- Integration, transfer, and closeout. Integration testing, administrator handoff, a production data-export test, the sustainability scorecard, and written post-engagement terms.
Your data is yours. You may demand a complete export of your data and content at any time, in an open machine-readable format, and receive it within ten business days. A production export test is part of closeout. Your data is never used to train models for other clients.
You keep what you fund. Where you fund the development of capability, you receive a perpetual, irrevocable, royalty-free license to keep using it for your own operations — surviving the end of the engagement. A nonprofit should not spend charitable dollars building an asset it retains no interest in, and we will not ask you to.
Nothing is described as available before it is. A capability is described to you, your board, your auditors, your funders, and your accreditors as available only after the corresponding increment has been accepted. Capability in development is labeled as in development. Always.
What you can run afterward
Your own administrator holds the platform roles, the backup and release log, and a tested export. If you leave, you take your data and you keep the right to use what you paid to build.
Through The Assessment, Implementation Coaching, and the Platform program.