Your Free Trial

Evaluate Rhenari with Your Team's Real Data

Use your 30-day free trial to test Rhenari against a real question about your organization's execution. Define what you want to learn, connect your tools, capture evidence, and build the case for a confident decision.

Follow this guide to:

• Define the execution question you want answered
• Connect your tools and scope a representative team
• Evaluate Rhenari's output against your existing processes
• Capture evidence and document outcomes for a confident purchase decision

To start your trial, subscribe through Microsoft Marketplace. By the end of this guide, you'll have a structured evaluation plan, clear results, and the evidence you need for a confident decision.

What's included in your trial

Your 30-day trial is the full Rhenari product with no feature restrictions. Everything available in your plan tier is active from Day 1:

• Continuous monitoring across all connected integrations — Microsoft Teams, Microsoft 365, Jira, and Azure DevOps
• Daily Momentum and Confidence scores delivered in your configured Teams channel
• Plain-language insights explaining what's driving acceleration or friction
• Proactive alerts for drift, anomalies, confidence gaps, and capacity signals
• Full access to the Rhenari workspace — Momentum trajectory, department-level views, structured decision and communication workflows
• Department scoping with role-based access (Admin and Viewer roles)

To learn how Rhenari works, see the product page. For setup instructions, see the Onboarding guide.

Trial limitations

The trial is time-limited, not feature-limited. A few characteristics of the product affect what you'll experience in the first 30 days:

• Baselines take time — Rhenari needs time to build a baseline of your organization's normal patterns. Confidence starts low and climbs as signal accumulates — meaningful readings take days, not hours.
• Team scope affects output quality — A small or inactive team will produce less signal, which limits pattern detection. Scope a representative, actively working team for the most useful trial.
• Tool coverage affects the picture — Connecting only one tool gives you a partial view. The more signal sources connected — communication, calendar, delivery — the more complete the execution picture.
• The trial window matters — A team in a quiet sprint, between planning cycles, or during a freeze period will generate less movement to detect. If your trial coincides with a low-activity period, the results may not be representative.

Before you begin

A successful evaluation starts with clarity about what you want to learn. Define your question, confirm your setup can answer it, and address any concerns before you start.

Define your evaluation goal

A focused trial produces clearer results. Before you start, identify the question you want answered by Day 30. The rest of the trial is structured around testing that question with real data.

Write your evaluation goal down. You'll return to it on Day 30 to assess whether the trial answered it.

Identify your primary use case

With your goal in mind, identify which Rhenari capability you should focus on during the trial. Rhenari can surface many patterns, but a focused evaluation produces clearer results. You can always expand to additional use cases after establishing initial success.

For detailed descriptions of each use case, see Use Cases.

Define your success criteria

What does a successful trial look like for your specific goal? Define this before you start — not at the end. You don't need quantitative targets. You need a clear statement of what would convince you.

• If your goal is roadmap alignment — Success means Rhenari's Momentum trajectory matched or challenged your understanding of how execution was tracking — and the insights explained why, in terms you recognized.
• If your goal is drift detection — Success means Rhenari flagged a divergence — drift, an anomaly, a confidence gap — before it surfaced through a status meeting, standup, or escalation.
• If your goal is coordination visibility — Success means Rhenari named a cross-team pattern — friction, collaboration shift, coordination overhead — that no one reported to you but that you or a peer recognized as real.
• If your goal is capacity monitoring — Success means Rhenari surfaced early indicators of strain — rising meeting load, after-hours patterns, friction spikes — before they became visible through attrition or missed deliverables.

Write your success criteria alongside your evaluation goal. These are the benchmarks you'll assess against on Day 30.

Scope your trial

The quality of your trial depends on three configuration decisions. Get these right and Rhenari has what it needs to produce meaningful output.

• Choose a representative team — Scope a department that reflects real work — active collaboration, in-progress delivery, regular communication. A test group or a team between projects won't generate the signal Rhenari needs to produce meaningful scores.
• Connect real tools — The minimum viable configuration: Microsoft Teams + Microsoft 365 + Jira or Azure DevOps. This gives Rhenari three signal types — communication, calendar, and delivery. Connecting only one tool produces a partial picture. The more signal sources active, the more complete the execution picture and the higher Confidence will climb.
• Pick the right window — Start the trial during an active period — mid-sprint, mid-quarter, during a planning cycle. A team in a quiet period, a holiday month, or a post-launch freeze will generate less movement, which limits what Rhenari can detect.

For step-by-step setup instructions, see the Onboarding guide. For details on what each integration reads, see Integrations.

Know what to explore

Rhenari's daily Momentum cards arrive passively — you don't have to go looking for them. But the full value of the trial includes features you need to actively explore. Use this table to guide your exploration based on your primary use case.

Plan your deliverables

Know what you're building toward before you start. If you need to justify the purchase decision to a manager, procurement, or IT, plan to capture these during the trial — not after it ends.

• Your evaluation goal and success criteria — the question you defined and whether the trial answered it
• 2–3 Momentum card screenshots — cards that named a real pattern, especially ones that surfaced something your status meetings didn't
• At least one alert example — an alert that arrived before the same information reached you through existing channels
• Decision impact — at least one decision you made differently because of a score, alert, or insight
• One-paragraph assessment — was the execution picture Rhenari delivered more complete than what you had before?

Common questions before starting

Run your evaluation

With your goal defined and your tools connected, here's how the evaluation unfolds — and what to do at each stage.

Suggested trial timeline

What kinds of things you'll see

Rhenari surfaces execution patterns your existing processes miss. During the trial, expect to see:

Document and decide

You defined your goal and planned your deliverables before the trial started. Now compile what you captured and make your assessment.

Review your evidence

Return to the deliverables you planned before the trial. Compile the screenshots, alerts, decision notes, and peer feedback you captured during the evaluation. Then write your one-paragraph assessment: was the execution picture Rhenari delivered more complete than what you had before?

Two honest checks before you decide:

• Did the trial answer your evaluation goal? — Compare what Rhenari surfaced against the question you set out to test. Did you learn something you wouldn't have known otherwise? Did you learn it early enough to act?
• Was the trial a fair test? — If the picture was familiar and nothing surprised you, check: was the configuration complete? Was the window representative? Consistent, high-Confidence Momentum aligned with the roadmap is a reading — not an absence of value. But an incomplete setup or a quiet month isn't a fair test.

Next steps after your trial

If you're sharing results with IT or procurement, forward the Security overview, FAQ, or Champion Guide — they're designed to answer the questions those teams will ask.