Product vs Network Boundary

TextCAD has two different kinds of project management. They should stay connected, but not mixed.

Product management belongs in the Product Wiki when it manages what to build: product scope, feature sequencing, coding progress, architecture, implementation risks, release readiness, technical decisions, and lessons learned from engineering.

Network and CRM management belongs in this wiki when it manages who to talk to and why: people, companies, target accounts, pilot status, meetings, follow-ups, investors, programs, events, competitors, outreach, and account strategy.

Keep In The Product Wiki

• product specs and roadmaps
• engineering track progress
• coding and deployment progress
• architecture decisions
• DFM and CAD research
• manufacturing knowledge
• technical validation procedures
• product-facing summaries of customer learning

Keep In The Network Wiki

• target company lists and account strategy
• pilot dossiers and follow-up state
• people and relationship notes
• meeting notes with external contacts
• incubators, accelerators, grants, and events
• competitor and market intelligence used for positioning
• EspoCRM workflow and outreach operations
• hiring and team-candidate relationship notes

Bridge Pages

Some pages should exist in both places, but with different depth.

The Product Wiki should keep compact summaries that explain how external learning changes the product. This Network Wiki should keep the full operational context, follow-ups, contact history, and account-level source trails.

Sources

• /network/08_Outreach_and_CRM/Go_to_Market/
• docs_network/03_Companies/
• docs_network/05_Pilots/