Outcome: a weekly partnership review that advances, pauses, or closes relationships from current evidence instead of activity volume.
Use this workflow for a curated set of strategic, technology, referral, ecosystem, or co-selling relationships. It is an internal operating review, not a replacement for a partner portal, formal deal registration, commission administration, or channel attribution.
Inputs
- Active partner organizations and relationship owners
- The current partnership thesis for each relationship
- Permitted meetings, messages, tasks, and documents
- Open commitments, decision dates, and unresolved risks
- Joint work already completed or approved
- Any formal program record that remains authoritative outside Finta
Evidence-gated stage model
Use stages as review states. Adapt them to the motion, and record the evidence required to leave each one.
| Stage | Evidence required to advance | Typical next decision |
|---|---|---|
| Thesis | A specific shared customer, audience, capability, or outcome | Is the idea worth validating? |
| Qualified | Relevant people and a plausible mutual benefit are verified | Should both sides spend time exploring it? |
| Mutual fit | Both sides have acknowledged the problem and value hypothesis | What should be designed together? |
| Joint design | Owners, scope, dependencies, and success evidence are explicit | Is the work ready for commitment? |
| Committed | Authorized owners accepted the work, timing, and boundaries | What must happen before activation? |
| Active | The agreed work is underway and outcomes can be observed | Continue, correct, expand, or stop? |
| Review | Results, costs, risks, and next options are documented | Renew, expand, redesign, pause, or close? |
Add Paused and Closed as visible outcomes. A relationship should not stay active merely because meetings continue.
Weekly review queue
Create one row per partnership that needs a decision this week.
| Field | Record |
|---|---|
| Partner and owner | Verified organization and accountable internal person |
| Current stage | The review state, not a sentiment score |
| Partnership thesis | One sentence describing the shared value |
| New evidence | Source-linked event, statement, document, or outcome |
| Open commitment | Who promised what, and by when |
| Blocker or risk | Missing authority, unclear value, dependency, privacy, commercial, or timing issue |
| Recommended decision | Advance, hold, redesign, pause, or close |
| Next approved action | Owner, recipient if any, due date, and review requirement |
Run the workflow
- Pull every partnership with an overdue commitment, upcoming decision, changed stakeholder, or stage older than the team's review threshold.
- Ask Aurora to gather the permitted CRM, meeting, message, task, and document context available through supported Finta tools.
- Require a source for every proposed stage change. Separate facts, reasonable synthesis, and unresolved questions.
- Compare current evidence with the exit criteria for the stage. Do not use email volume, meeting count, or executive seniority as a substitute.
- Review ownership and commitments. Move work to another owner only after the receiving person accepts it.
- Choose one decision: advance, hold, redesign, pause, or close.
- Review proposed CRM changes, tasks, meeting briefs, or external drafts before saving or sending consequential work.
- Preserve the reason for the decision so the next review starts with what changed.
Aurora prompt
Review the active strategic-partnership pipeline using the permitted CRM records, meetings, messages, tasks, and documents available to you. Build a decision queue for relationships with new evidence, overdue commitments, upcoming decisions, or stale stages. Cite the source for every proposed stage change. Separate verified facts from hypotheses, recommend advance, hold, redesign, pause, or close, and prepare the smallest useful next action for review. Do not infer consent, authority, relationship strength, commercial acceptance, or partner-sourced revenue. Do not send messages or make commitments without approval.
Aurora can inspect supported Finta records, synthesize available context, research public information, prepare briefs and drafts, propose record changes, and complete eligible actions. Tool access, organization permission, connected sources, and human review determine what it can safely complete.
Worked example
A software company is exploring a joint customer workshop with an accounting platform. The relationship has been labeled “active” for six weeks because the teams held four meetings. The latest notes show that both sides agree on the audience, but neither has approved a date, speaker, customer list, or success measure.
Aurora gathers the permitted records and identifies two completed commitments and three missing decisions. It recommends moving the relationship from Mutual fit to Joint design, not Active. It prepares a review brief with the open decisions and drafts an internal task for the partnership owner to confirm authority and scope with the counterpart.
The owner corrects the proposed counterpart role, approves the internal task, and holds the external draft until the marketing lead confirms what can be shared. At the next review, the teams either document the agreed plan and advance, or pause the relationship with a reason and a revisit date.
Completion checks
- Every stage change has source-linked evidence.
- Activity is not presented as partnership progress.
- Every open commitment has an owner and date.
- Missing authority, consent, or sharing permission is visible.
- Paused and closed relationships retain their decision history.
- External messages, material record changes, and commitments were reviewed.
- Formal deal-registration, incentive, or attribution data remains in its authoritative system.
Safe stops and limitations
Stop when the partnership thesis, decision authority, information-sharing boundary, or source record is unclear. Meetings can be positive without producing mutual commitment. Communication context may be incomplete. One company may use different lifecycle terms, and a co-selling opportunity may need a separate program-owned record.
Finta can be configured to coordinate relationship context, stages, and follow-through. It is not a PRM portal, commission engine, or proof of channel-sourced revenue.
Sources
- Finta CRM
- Finta Aurora
- Salesforce Partner Relationship Management
- Microsoft co-sell opportunity stages
- AWS Partner Central opportunity stages
- ISO 44001 collaborative business relationship management
Run a partnership review with evidence
Configure a pipeline around the decisions your team actually makes. Explore Finta for strategic partnerships.