Questions, answered properly

An app that turns the contacts already associated with a HubSpot company into an editable org chart with a stakeholder heatmap, and writes the reporting structure back into your portal as real HubSpot associations.

Not yet. We are preparing a listing, and HubSpot decides whether and when it is approved — so we will not promise a date. Right now we install Rehnable directly for a limited number of portals during early access. Everything on this site describes the product as it actually works today, not a plan.

Email hello@rehnable.com with your HubSpot portal ID and roughly how many people would use it. You get an install link back, and a Super Admin in your portal completes the OAuth install.

Minutes. Approving the install is one screen; the association labels and the team property are created automatically; assigning seats takes as long as picking names from a list. There is no import and no data preparation.

No. The one thing that matters is that contacts are associated with the company record — that association is how Rehnable knows who belongs to a company. Job titles help but are not required, and nothing needs cleaning up before you start.

A HubSpot Super Admin, because installing an app and granting permissions requires that level of access. After the install, ordinary users only need a seat.

The core interaction is dragging one card onto another. Most people are productive within a few minutes; the how-to guide covers the rest, and it is short on purpose.

Yes — ask for a walkthrough and we will show you the editor running against sample data. We deliberately never demo against a real customer's CRM.

From the Rehnable card on a HubSpot company record. One button opens the editor in a modal over the record. Launching from a contact record is planned but not available yet.

No, and that is deliberate. Guessing reporting lines from job titles produces confident nonsense — "Director" over "Senior Manager" is wrong about half the time. Rehnable shows what your CRM knows and makes it fast for a human who knows the account to build the truth.

As a labelled contact-to-contact association in your portal: Manager one way, Direct report the other. It appears on the contact record itself and is usable in lists and workflows like any other association.

There is no Save button. Each drop is written to HubSpot immediately and can be undone with Cmd/Ctrl+Z or the undo toast. Nothing is left in a draft state you might forget to commit.

Not today — one primary manager per person. Dotted-line and secondary reporting relationships are a planned addition rather than a hidden setting.

Leave them in the contacts panel — only the people you place appear on the canvas. If they are already placed, remove them from the chart; that clears their reporting lines and leaves the contact record itself untouched.

They stay visible instead of silently disappearing off the canvas, so you can re-parent them deliberately. The whole operation is undoable.

No. Dropping a manager onto their own subordinate is refused by the canvas, and the server validates the same rule again before writing — the client is never the last line of defence.

They can, and writes go to HubSpot in the order they happen. What is not there yet is live refresh — you will not see a colleague's change until you reopen the editor. Reconciliation for simultaneous editors is on the roadmap.

There is no hard product limit, and licensing is never based on contact count. In practice a chart with hundreds of nodes stops being readable long before it stops rendering — pick who matters, that is the point of the tool.

Grouping people by function — Procurement, IT, Finance — independently of the reporting structure, because buying committees cut across the org chart. Team membership is stored in an ordinary contact property, so it works in lists and workflows too.

Name and job title, plus up to four contact properties you choose for the whole portal — buying role, lifecycle stage, last activity, or any other dropdown, number, date or yes/no property in your schema. Cards grow to fit what you selected.

Three modes, one at a time. Engagement is days since the contact's last sales activity, mapped over a 120-day window. Deals is how many deals the contact is associated with. Combined is the mean of the two, and it is the default.

Scores are normalised within the company you are viewing. An absolute scale would render every small or quiet account uniformly cold and tell you nothing. Relative scoring always separates the warmest stakeholders from the coldest ones in the account in front of you.

hs_last_sales_activity_timestamp — HubSpot's own field for the last sales activity on a contact. One cheap batch read covers the whole chart, which is why opening a chart is fast.

No. Heat is calculated across the whole company, not the visible subset, so hiding part of the tree never recolours the part you are still looking at.

No — the underlying number is printed on the card, and team membership is shown separately from heat. Colour alone is never load-bearing, which also makes the chart usable if you have trouble distinguishing certain hues.

It reads HubSpot's own hs_buying_role property and shows it on the card. You can update it through bulk property editing like any other writable property; there is no separate buying-role editor.

No. Rehnable works exclusively on the data in your portal. It will not tell you about people who are not in your CRM — if you need external org data, you need a data provider, and that is a different product.

A reporting line pointing at a contact that no longer exists is treated as absent and reported — not as a crash. Re-parent the affected reports and the chart is clean again.

Everything Rehnable writes is standard HubSpot data — associations and properties — so it is available to lists, workflows and reporting to the same extent HubSpot exposes those object types generally.

Rehnable uses standard CRM objects, associations and custom association labels. If you are unsure whether your subscription level includes what it needs, send us your portal ID before you buy anything and we will check it against your actual portal rather than guess from a plan name.

Yes — a sandbox is a good place to try it. Bear in mind sandboxes usually contain little activity data, so the heatmap will look flat there.

It should not. Rehnable adds its own association labels and one contact property, and it batches and throttles its API calls to stay inside your portal's rate limits so other integrations are not starved.

It never rewrites properties you did not ask it to. Bulk property editing changes exactly the property you selected on exactly the contacts you selected — and changing someone's manager never silently changes their team, or vice versa.

Not currently. Rehnable works with contacts, companies and deals. Custom object support is not on the near-term roadmap.

HubSpot's own parent/child company associations. If your group structure is not modelled there yet, you can build it in the group view by dragging companies onto each other.

The editor is built for the desktop CRM, where the modal and drag-and-drop belong. Reporting lines written by Rehnable are visible on contact records in the HubSpot mobile app, because they are ordinary associations.

Current versions of Chrome, Edge, Safari and Firefox. The app runs inside HubSpot's own iframe modal, so if HubSpot works in your browser, so does Rehnable.

No. Contacts, companies, deals and activity are read live for the chart you have open and never written to our database. What we store is an encrypted OAuth token, your portal's configuration, seat assignments and subscription status. The security page has the complete list.

Microsoft Azure, Sweden Central — inside the EU. Your CRM data stays wherever your HubSpot account hosts it.

Which portals use Rehnable and which users hold seats. Not a single customer record, because those never arrive on our side in the first place. That is the whole reason the architecture is shaped this way.

Refresh tokens are encrypted at the application level with AES-GCM, and the key is held in Azure Key Vault. Access tokens are short-lived, refreshed server-side and never sent to the browser.

Be aware of this before handing out seats: a seat holder can see the org charts and CRM data the app can read, regardless of their own HubSpot record-level permissions. If that is a problem for your setup, tell us — it is exactly the kind of feedback that shapes what we build next.

You are the controller, we act as a processor, our infrastructure is in the EU, and a DPA listing Azure and Stripe as subprocessors is available on request. Because we hold no CRM data, erasure and access requests are handled entirely inside your own HubSpot portal.

No, and we will not imply otherwise. What we offer instead is an architecture in which your sensitive data never reaches us, plus a straight answer to any security question you send.

No. We do not store your CRM data at all, so there is nothing to train on, sell, or share.

Email hello@rehnable.com. You will get a confirmation, a fix, and an account of what we did.

Four seat packages: Starter 5 seats at $39/month, Team 15 at $99, Business 40 at $199, Enterprise 100 at $399. Annual billing is about 15% cheaper. Every package contains the complete product — see the pricing page.

Yes — 14 days of the full product, with no card and no payment details collected up front.

Not while we are in early access ahead of the Marketplace listing. The prices we publish are what billing will start at, and nobody will be charged without hearing from us first.

A named HubSpot user who can open the editor. Colleagues who only read the reporting lines on contact records in HubSpot do not need a seat, because those are ordinary CRM associations.

Not yet — the packages are 5, 15, 40 and 100. A twelve-person team buys the 15-seat package. Individual add-on seats were deliberately left out of the first version to keep billing simple; we will add them if customers actually ask.

Yes. An admin can take a seat from one user and give it to another at any time — useful when someone leaves or changes role.

Access continues while the payment is being retried, so an expired card does not lock your team out mid-quarter. Only a genuinely cancelled or unpaid subscription ends access.

The editor stops opening. Nothing in your portal is deleted or held hostage — the reporting lines, teams, lists and tasks are your data and stay exactly where they are.

Checkout runs on Stripe's hosted page. We never see or store card details — only a subscription reference and its status.

All prices exclude VAT. What ends up on your invoice depends on where your business is registered and whether you supply a valid VAT number — businesses inside the EU but outside Sweden are normally invoiced under the reverse-charge mechanism, and customers outside the EU are invoiced without Swedish VAT. If you need the exact treatment for your country before you buy, ask us.

Above 100 seats there is no self-serve tier, on purpose — talk to us and we will sort out the commercial and procurement side properly.

Two things, once: a labelled contact-to-contact association pair called Manager / Direct report, and a contact property called orgchart_team. Both are created idempotently — nothing is duplicated if they already exist.

The next write notices, re-creates what is missing and retries automatically. You do not have to call support to recover from an accidental deletion.

The contacts are almost certainly not associated with the company record. Rehnable reads the association, not the email domain — add the association and reopen the chart.

Usually they do not hold a seat. Check Settings → Seats. If the whole portal is affected, the app may have been uninstalled or the subscription may have ended.

It means the editor is running against built-in sample data rather than your CRM. The banner is persistent and cannot be dismissed, precisely so demo data can never be mistaken for your real portal. Turn Test mode off to go back to live data.

From HubSpot's connected apps settings, like any other app. Your authorisation is revoked at once; a credential already issued to us can remain valid for up to about 30 minutes, after which the installation is marked as removed and our copy of your token is deleted. Everything Rehnable created inside your portal stays there — and you can delete the labels and the team property yourself if you want no trace left.

Email hello@rehnable.com with your portal ID and what you were doing. During early access you are writing directly to the person who built the thing.

Launching from contact records, dotted-line reporting, and live refresh when several people edit the same chart. Early access customers have real influence over that order.

Not yet. It is parked rather than rejected — we build features when customers ask for them, and this one has not come up enough yet. If you need it, say so and it moves up.

No plans. Rehnable is built deeply into HubSpot's association model rather than on a lowest-common-denominator abstraction, and that depth is most of what makes it good.

An independent Swedish software company of the same name. Rehnable is built by people who run HubSpot for a living, which is why it solves the problem the way a CRM manager would want it solved.

No. Rehnable is an independent app built on HubSpot's public developer platform, and is not affiliated with or endorsed by HubSpot, Inc.

Email it. There is no feedback portal to shout into — requests go to the person who decides what gets built, and during early access the loop from suggestion to shipped is unusually short.