Skip to content
Romy.
Open menuClose menu
Sign inStart First Users

CRM & Relationships

Know who matters and the next relationship action.

Romy is the relationship layer for product builders. It keeps every person connected to the conversations, commitments, and Goals behind why they matter, brings the context back when it counts, and prepares the next growth action. You approve every external follow-up.

Start First UsersSee how Romy works
RelationshipsMonica Hall

Monica Hall

VP Growth · Raviga

Decision makerOpen proposal
Follow-up due

Here's what Romy knows

Monica owns Raviga's decision on a proposal worth $2.4k MRR. Closing it covers twice this month's remaining gap.

Last meaningful interaction
Re-grouping with Gavin Belson on Wednesday.
Open commitment
Follow up after the internal decision meeting.

Recent history

  1. Proposal opened for the fourth timeNo reply yet · $2.4k/mo
  2. Meeting with Gavin Belson plannedMonica was re-grouping internally
  3. Funk and Fermentation Fest mentionedSalesforce Park · this weekend

Your inbox isn’t a relationship system.

The relationship starts in a comment or an email. Notes land somewhere else. The meeting goes into the calendar. A promise becomes a vague reminder.

  1. The contact record says who the person is, but not why they matter.
  2. The thread remembers the words, but not the Goal or decision behind them.
  3. The reminder says “follow up,” but not what was promised or what would be useful.
  4. You’re constantly re-building the relationship from memory.

You don't need more fields. You need the relationship and the next step brought back together.

Open with the briefing.

Romy brings the person, the commercial reason, and the live commitments into one calm sequence.

See how Romy finds the reason to communicate

  1. Bring the relationship together: connect the person, company, permitted conversations, meetings, notes, and available source context.

  2. Connect the reason: show the audience, Goal, opportunity, project, deal, or relationship role that makes the person relevant.

  3. Return to context: surface the last meaningful moment, open promises, recent changes, and only the company knowledge needed now.

  4. Recommend and prepare: explain one useful next action, or a deliberate no-action, then prepare the relevant follow-up or internal work.

  5. Preserve the result: connect the response, meeting, task, project, product use, or commercial outcome back to the relationship and plan.

People aren’t pipeline rows.

Ironwood is testing whether trusted craft creators can become a profitable growth route. Romy recommends a learning conversation and rejects the premature affiliate pitch.

IronwoodGoal · Learn the creator route before scaling it
Romy

Three relationships need your attention today. Each has a different reason, and a different next move.

You

Show me Ron.

  1. Creator conversationRon Swanson · 3 days agoRelationship briefing

    Ron’s readers match the current buyer. Learn what they need before asking for a promotional commitment.

    Open the relationship briefing

    Start with a learning conversation, not an affiliate proposal.

    Ron’s audience matches Ironwood’s first-time cast-iron buyer. The relationship is early, so the useful next step is to learn before asking for promotion.

    Why this relationship matters now

    A paid pitch would spend the relationship before Ironwood has evidence of fit. A focused conversation keeps the learning goal, the audience, and the approval boundary together.

    Prepared follow-upUser review · ready to editReady for your approval

    Learning request · Ron Swanson

    Hi Ron, your point about pre-seasoned pans still needing real care stuck with me. I’m testing an approach to cast-iron for people buying their first proper pan.

    Would you be open to a 20-minute learning conversation about what people get wrong when they buy one? I’ll share the seasoning guide either way. No partnership pitch.

    Discard · Edit · Approve for copy

  2. Beta feedbackAndy Dwyer · 5 days agoRelationship briefing

    Andy found a handle-heat problem. Ask where it happened and retain the product context.

    Open the relationship briefing

    A beta note is a product relationship, not a lead.

    Andy reported that the skillet handle gets too hot. The useful move is one specific product question, not an upsell or a sales sequence.

    Why this relationship matters now

    This relationship matters because it improves the product. Keeping the feedback attached to the person makes the next response useful and preserves the context for Knowledge.

    Prepared replyUser review · ready to editReady for your approval

    Handle follow-up · Andy Dwyer

    Thanks for flagging the handle heat, Andy. Was it on gas or electric, and how long into the cook?

    This is exactly the kind of note that changes the product. I’ll close the loop once we have looked into it.

    Discard · Edit · Approve for copy

  3. Advisor commitmentLeslie Knope · 3 weeks agoRelationship briefing

    Leslie is waiting for the update you promised. Keep that commitment before opening another conversation.

    Open the relationship briefing

    Keep the update you promised before making another ask.

    Leslie opened two chef introductions and asked to hear how the creator learning is developing. The open commitment sits with the product builder.

    Why this relationship matters now

    The relationship stays useful when Ironwood honours what it said it would do. The next action is an honest update, not a fresh request attached to the old promise.

    Prepared updateUser review · ready to editReady for your approval

    Promised update · Leslie Knope

    Hi Leslie, the update I owe you: the creator angle is bringing qualified store visits, though contribution margin is still uncertain, so we are keeping the first test small.

    Both introductions were genuinely useful. Thank you, I’ll keep you posted as the numbers firm up.

    Discard · Edit · Approve for copy

A relationship can matter without becoming a lead.

A beta user, customer, creator, partner, supplier, advisor, or investor can each matter for a different reason. Romy keeps that reason legible without forcing every person through one sales funnel.

  • Beta user
  • Customer
  • Creator
  • Partner
  • Supplier
  • Advisor
  • Investor
Correction

Change the relationship type, source context, recommendation, or commitment when Romy has it wrong.

Boundary

Accepting one recommendation doesn’t grant blanket sending authority. External messages and consequential record changes retain the applicable product builder approval.

Privacy

Only use connected or imported relationship data within the permissions of the workspace. Imported and inferred information isn’t guaranteed to be true.

Bring your relationships back into the work.

Keep the relationship, the reason it matters, and the next useful action in one place.

Start First UsersSee how Romy works

Your growth, connected.

Everything behind your growth, in one connected system.

Growth strategy

Turn market signals into a focused plan.

Content

Create and reuse work that supports the plan.

Relationships

Keep people, conversations, and opportunities connected.

Knowledge and context

Give every decision the right product and customer context.

Tasks, Projects, and Money

Turn decisions into work while keeping the business in view.

Each relationship decision makes the next recommendation smarter.

What Romy sees, suggests, and what you decide stay with the relationship, so the next action starts with the last one’s context.

  1. Signal

    A trusted creator engages with the product builder’s specific point about fit.

  2. Recommendation

    Begin with a learning conversation, not an affiliate proposal.

  3. Judgment

    Product builder removes a superlative, protects the learning purpose, and caps the first test.

  4. Action

    The conversation, sample, and fit-education test go ahead under explicit approval.

  5. Result

    Qualified visits improve, but contribution margin remains uncertain.

  6. Smarter next

    Retain the audience and expert-fit hypothesis; limit spend and run a smaller tracked test.

Then the loop returns to the next signal.

Good ideas for the bit after shipping.

Practical thinking on positioning, distribution, outreach, and the commercial work that turns a product into a business.

Explore Romy insights
music product launch video
Distribution

Most launch videos are boring. I made mine a musical in 2.5 hours.

internal tool pivot
Product Validation

When the internal tool is better than your actual product (best ever pivots)

AI-blindness
Distribution

People are going AI-blind. Here are the tools that'll still get you noticed.

Questions worth answering.

What is Romy’s CRM?

It is the relationship layer inside Romy’s go-to-market system. It keeps a person or company connected to why they matter, the useful history, current commitments, and the next action.

Who can I keep in it?

Customers, beta users, creators, partners, suppliers, advisors, investors, and sales prospects. Not every relationship needs a deal stage.

Does Romy provide contact data?

Romy isn’t a purchased contact database. Imported and suggested context stays inspectable, permissioned, and correctable, and always names its source.

Can I import an existing CRM or spreadsheet?

Yes. Romy imports from CSV, and shows the exact source of every record so you can review what arrived.

How are email and meetings connected?

Where a permitted integration is available, relevant messages and meetings can inform the relationship record and briefing. Romy mustn’t imply universal capture or hidden recording.

What does a relationship briefing include?

The person, why they matter, relationship role, last meaningful interaction, current Goal or project, open commitments, relevant context, and one recommended next action.

Does Romy send follow-ups without approval?

No. Romy prepares the follow-up. You edit, approve, reject, and perform the available send or copy action. One approval isn’t blanket authority.

Can Romy replace my current CRM?

It may replace a light founder CRM when relationship continuity and connected work are the main need. It isn’t designed to replace advanced enterprise sales operations, territory planning, or forecasting.

Is CRM separately priced?

No. CRM & Relationships is part of the complete Romy system.

What will beta cost?

Romy is free during beta. Billing isn’t open. The planned public-launch price is $49/month, billed monthly.

One plan for the complete Romy system.

Romy reads your market, builds the plan, prepares the work, and never moves without your approval.

  • A growth plan tied to the result you need.
  • The next growth actions ranked, explained, and prepared.
  • Relationships, content, tasks, time, money, and knowledge connected.
  • Your approval before anything represents you or makes a commitment.
  • Your judgement and the result improving what Romy recommends next.

Beta access · no charge yet

Every capability included.

Billing isn’t open. The planned public-launch price is $49/month, billed monthly.

Start First Users