01
Organization
The primary record for a church, school, homeschool organization, publisher, ministry, nonprofit, association, or strategic media partner.
Formationly Executive Operating System
Kingdom Relationship Management
The stewardship-centered architecture for preserving organizational knowledge, coordinating ministry relationships, and supporting responsible follow-up across Formationly.
KCRM Architecture • Version 1.0 • July 2026
Purpose of KCRM
Relationships should be stewarded with continuity, clarity, and accountability.
Kingdom Relationship Management will become Formationly’s ministry-centered relationship platform. It will preserve the history of churches, homeschool organizations, schools, publishers, ministries, strategic partners, and individual contacts.
KCRM is not simply a sales pipeline. It is an organizational memory system designed to protect relationships, support partners, strengthen follow-up, and preserve ministry continuity.
Stewardship Model
Relationship authority is shared through clearly defined responsibilities.
Formationly
Owns the Record
Formationly retains the organizational record, complete activity history, governance authority, and responsibility for long-term continuity.
Partner
Stewards the Relationship
The assigned partner communicates with the organization, records meaningful activity, completes follow-up, and represents Formationly responsibly.
Administrator
Governs the Lifecycle
Administrators control reassignment, merging, archival, restoration, permissions, compliance review, and permanent deletion when authorized.
Core KCRM Records
The relationship platform is built around connected records.
02
Contact
A person associated with an organization, including pastors, administrators, educators, parents, editors, ministry leaders, and decision-makers.
03
Relationship
The ongoing connection between Formationly, an organization, its contacts, and the assigned partner or team.
04
Conversation
A documented call, meeting, email exchange, presentation, conference interaction, introduction, or meaningful discussion.
05
Task
A specific action assigned to a partner or administrator with an owner, priority, due date, status, and completion record.
06
Follow-Up
A scheduled relationship action created after a conversation, presentation, resource delivery, commitment, or request.
07
Note
Internal contextual information that supports continuity, preparation, organizational understanding, and responsible relationship management.
08
Opportunity
A potential partnership, presentation, pilot, strategic collaboration, referral pathway, or ministry expansion opportunity.
09
Activity
A timestamped event that becomes part of the permanent relationship timeline.
Relationship Lifecycle
KCRM should support the full ministry relationship journey.
Identified
→
Introduced
→
Listening
→
Exploring Fit
→
Partnership
→
Ongoing Stewardship
The lifecycle should describe the health and maturity of the relationship without forcing every organization into a traditional sales funnel.
Organization Record
Every organization should have one authoritative record.
IDENTITY
Organization name, type, website, location, mission, size, and current status.
ASSIGNMENT
Assigned partner, supporting team members, administrator, region, and date assigned.
RELATIONSHIP
Relationship stage, health, source, introduction path, priorities, and known ministry needs.
CONTACTS
Primary contact, additional leaders, decision-makers, influencers, and preferred communication channels.
ACTIVITY
Conversations, presentations, resources shared, notes, tasks, follow-ups, and partnership milestones.
GOVERNANCE
Record ownership, permissions, audit events, reassignment history, archival status, and duplicate review.
Permanent Activity Timeline
Relationship history should survive personnel changes.
The timeline becomes the authoritative chronological history of the relationship.
Record creation, assignment, reassignment, merge, archive, and restoration.
Calls, meetings, emails, presentations, introductions, and conference interactions.
Tasks created, completed, overdue, cancelled, or reassigned.
Resources sent, partnership milestones, decisions, commitments, and follow-up activity.
Permission Framework
Access should reflect responsibility.
| Capability | Partner | Premier Partner | Administrator | AI Guide |
|---|---|---|---|---|
| View Assigned Records | Yes | Yes | Yes | Context Only |
| Create Organization or Contact | Yes | Yes | Yes | No |
| Update Assigned Records | Yes | Yes | Yes | Suggest Only |
| Reassign Ownership | No | Limited | Yes | No |
| Archive Record | Request | Request | Yes | No |
| Permanently Delete | No | No | Authorized Only | No |
Governance Rules
Organizational memory must be protected.
Partners cannot permanently delete organizational records, contacts, conversations, or activity history.
Potential duplicates should be reviewed and merged instead of maintaining competing histories.
Reassignment should preserve the prior partner, date, reason, open tasks, and full relationship timeline.
Archived records should remain searchable by authorized administrators and should be restorable.
Sensitive notes and personal information should be limited to legitimate ministry and operational purposes.
AI Relationship Assistant
AI should strengthen preparation and follow-through.
Prepare a briefing before a meeting.
Summarize verified prior activity.
Suggest discovery questions based on the organization type.
Identify overdue commitments or follow-ups.
Recommend approved resources for the current relationship stage.
Draft a follow-up for partner review without sending it automatically.
KCRM Boundaries
The system should support relationships without reducing people to transactions.
KCRM should not encourage manipulative pressure, artificial urgency, or relationship scoring that conflicts with Formationly’s ministry-first philosophy.
Prayer requests, pastoral concerns, family information, and sensitive notes should be handled with appropriate restraint and permissions.
AI-generated summaries and recommendations should never be treated as verified facts unless grounded in the record.
Relationship health should be evaluated through responsiveness, trust, mutual fit, service, and progress—not revenue alone.
Implementation Stages
KCRM should be developed progressively.
STAGE 1
Data Foundation
Define organizations, contacts, ownership, stages, permissions, required fields, and governance rules.
STAGE 2
Core Workspace
Build organization records, contact profiles, notes, conversations, tasks, and activity timelines.
STAGE 3
Workflow & Governance
Add assignments, reassignment, duplicate review, archival, audit history, alerts, and approvals.
STAGE 4
Relationship Intelligence
Introduce meeting preparation, summaries, recommendations, relationship insights, and executive reporting.
KCRM Success Measures
Success is measured through relationship stewardship.
Fewer duplicate organization and contact records.
Greater completion of meaningful follow-up commitments.
Better continuity when partners change or depart.
More complete relationship histories and contact information.
Stronger preparation before meetings and presentations.
Clearer visibility into ministry relationships and organizational health.
Relationships are stewarded. History is preserved. Ministry continues.
KCRM will give Formationly a responsible framework for preserving ministry knowledge, supporting partner follow-through, protecting relationship continuity, and serving organizations with greater preparation and care.