Your first 30 days

Put Rhenari to the test against your own plan.

Define the question, connect your tools, and gather the evidence for a confident decision. Not the right fit? Opt out within 30 days for a prorated refund.

Follow this guide to:

• Define the question about your plan you want answered
• Choose what Rhenari covers first and connect your tools
• Compare what Rhenari tells you with what you hear today
• Capture the evidence for a confident decision

Subscribe directly or through Microsoft Marketplace. If Rhenari isn't the right fit, opt out within your first 30 days for a prorated refund. This applies to your first Focus or Full subscription.

How to use this guide

This guide walks you through your first 30 days in three parts:

Treat your first 30 days as an experiment. Be curious, ask questions, and write things down.

Everything in your plan, from Day 1

Your first 30 days are the full product. Everything in your plan is active from Day 1:

• A daily reading of the work across every connected tool, against your plan
• Daily Momentum and Confidence, delivered in Teams, Slack, Google Chat, or email
• Plain-language insights on what's moving the work forward and what's creating friction
• Alerts when drift appears, with the cause, the evidence, and the move that's yours to make
• The Rhenari workspace: Momentum trend, department views, and the insight feed
• Department scoping with Admin and Viewer roles

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

What shapes your first 30 days

Nothing is held back during your first 30 days, but a few things affect what you'll see:

• Baselines take time. Rhenari learns what normal looks like for your organization. Confidence starts low and climbs as evidence builds, so meaningful readings take days, not hours.
• Coverage matters. A department with little activity gives Rhenari less to read. Cover the departments where your plan's priorities live.
• Connected tools matter. One tool gives a partial picture. The more you connect, the more complete the picture and the higher Confidence climbs.
• Timing matters. A quiet stretch between planning cycles, a holiday month, or a freeze gives Rhenari less to read. If your first 30 days fall in one, the results may not be representative.

Before you begin

A useful evaluation starts with a clear question. Define it, confirm your setup can answer it, and raise any concerns before you start.

Define your question

Before you start, name the question you want answered by Day 30. Everything else in your evaluation tests that question against real work.

Write it down. You'll come back to it on Day 30.

Choose your focus

See Use Cases for more on each.

Decide what would convince you

Decide what success looks like before you start, not at the end. You don't need numeric targets, just a clear statement of what would convince you.

• If your question is whether the plan is on course: Momentum and its insights matched or challenged your sense of how the plan was going, and explained why in terms you recognized.
• If your question is timing: Rhenari flagged drift before it reached you through a status meeting, report, or escalation.
• If your question is cross-team friction: Rhenari named a pattern between teams that nobody reported to you, and that you or a peer recognized as real.
• If your question is capacity: Rhenari showed a department's conditions shifting before the strain turned into missed deliverables.

Write your success criteria next to your question.

Choose what Rhenari covers first

Three decisions shape the quality of your first 30 days:

• Cover where the plan lives. Start with the departments carrying your plan's priorities, where work is active and in progress. A test group or a team between projects gives Rhenari little to read.
• Connect real tools. Rhenari reads three kinds of source: communication (Teams, Slack, Google Chat), calendar (Microsoft 365, Google Workspace), and delivery (Jira, Azure DevOps, Linear, and similar tools). Connect at least one of each.
• Pick an active window. Start mid-quarter or during a planning cycle, not in a quiet stretch.

Your onboarding session covers these choices with you. For setup steps, see the Onboarding guide.

Know what to explore

Your daily Momentum card comes to you. The rest is worth exploring on purpose.

Plan your evidence

Know what you're building toward. If you'll need to make the case to your leadership team, IT, or procurement, capture these as you go:

• Your question and success criteria, and whether your first 30 days answered them
• Two or three Momentum cards that named something real, especially anything your status meetings missed
• At least one alert that reached you before the same news arrived another way
• At least one decision you made differently because of a reading, alert, or insight
• A one-paragraph assessment: was the picture Rhenari gave you more complete than what you had before?

Common questions before you start

Run your evaluation

With your question set and your tools connected, here's how the 30 days unfold.

Week by week

What you'll see

Document and decide

You set your question and planned your evidence before you started. Now pull it together.

Review your evidence

Gather the cards, alerts, decision notes, and peer feedback you saved. Then write your one-paragraph assessment: was the picture Rhenari gave you more complete than what you had before?

Two honest checks:

• Did it answer your question? Did you learn something you wouldn't have known otherwise, early enough to act?
• Was it a fair test? If nothing surprised you, check the setup. Were the right departments covered, the tools connected, and the window representative? Steady, high-Confidence Momentum on a plan that's on course is a reading, not an absence of value. But an incomplete setup or a quiet month isn't a fair test.

After Day 30

Sharing results with IT or procurement? Forward the Security Overview, FAQ, or Champion Guide.