Discuss a Project
Begin with the operating context.
The first conversation begins with the operating context — not a product pitch. It is a working discussion of how your organization operates, what it runs on today, and what the system must carry, before any technology is proposed.
A useful first message
What to include.
A few lines on each of these lets the first conversation start from substance. Incomplete is fine — the discussion fills the gaps.
- Organization
- Institution, enterprise or group — and its approximate size and structure.
- Operating environment
- The domain the system serves: administration, finance, logistics, case work, operations.
- Current systems
- What is in service today, and what must remain.
- The primary problem
- What the organization cannot see, control or prove today.
- Required integrations
- Registries, applications or data sources the system must connect to.
- Deployment expectations
- On-premises, private environment or cloud — and who must control the data.
- Approximate timing
- When a decision is expected, and any fixed constraints.
- Preferred contact
- Who to reach, and how.
Do not send sensitive, confidential or protected operational information through public email. Describe the environment at a general level; detailed material belongs in an appropriate controlled setting once a conversation is established.
Two starting points
Institutional system, or continON.
For a purpose-built institutional system, the conversation starts from mandate, records and accountability. How institutional systems are delivered →
For continON, it starts from your structure, departments and current applications — and typically leads to a demonstration configured around them. The continON platform →
One project channel.
Institutional systems and continON begin with the same requirement: understand what the organization must be able to operate, control and carry forward.