We sell outcomes. Not hours.
A product-led signup that turns into a paying team without anyone talking to it. An enterprise deal with a security review and procurement in the way. Same product, same company record, two completely different data shapes. Product-led growth only works when the usage data reaches the people who act on it, and most CRMs never see it. Fiverr ran its B2B business across two HubSpot portals for exactly this reason. We merged them into one, and three contract expansions later we still build on it. Our prices are published.
Four things a generic implementation gets wrong.
Signups, activation, seats and usage are product events, and in a PLG motion they are the whole story. Stages, approvals and security reviews are deal events. The object model has to hold both on the same company, with usage from Amplitude, Mixpanel or Segment landing as properties and timeline events, so segments, nurture and rep alerts run off real behaviour instead of a rep typing product data in by hand.
One free signup from a work email is a footprint at an account, and the account is what gets qualified. The SDR-to-AE handoff has written criteria, or every signup becomes a deal and the forecast stops being believed.
Seats, tiers, renewals. Sales, CS and finance have to look at the same account and see usage and contract side by side, or expansion gets found by accident at renewal.
Zendesk, Outreach, Sales Navigator, billing, product analytics. HubSpot is the system of record, and the rest connect to it. Marketplace connectors and custom integrations keep the tools your teams already like, without a second CRM in the middle.
Fiverr's B2B business ran across two separate HubSpot instances, Fiverr Pro and Enterprise. Two sets of processes, two sets of data, and no single view for the sales operations team. Merging them meant reshaping workflows, automations and the integrated stack without disrupting active sales.
We merged the two instances into one portal, rebuilt the stack around it, and kept going: marketing automation support, a new portal scoped for the Affiliates team, a custom HubSpot Inbox channel wired to Fiverr's internal inbox, and a new HubSpot public app. First meeting to signed SOW took about five weeks. Read the story →
"The work with Penguin exceeded our expectations. Their proactive approach and attention to detail made a potentially complex transition feel smooth and manageable."
Mor Cohen Zymler, Director of Sales Operations, Fiverr · public HubSpot Directory review · Read the story →A hyper-growth AI platform provider, name withheld at their request, had HubSpot in place and used it by hand. Unqualified leads went straight into deals. Here is what changed.
Four steps, in this order.
Fiverr Pro and Enterprise consolidated into one HubSpot, then a custom Inbox channel, an Affiliates portal and a public app.
Qualification pipeline, written handoffs, approval gates and rebuilt attribution. Penguin embedded week to week on reporting and RevOps since.
Every outcome has a price on it, published here, on our pricing page and inside our calculators. A two-motion build is scoped from the same components; the calculator shows the working.
Starts at $40k for one hub with your data in it and your team working there, starting fresh. Coming off Salesforce, Marketo or two portals of your own adds a flat $25k however many systems you are leaving, so the smallest migration is $65k. Each further hub is $25k, and the migration calculator prices your exact stack.
A report and a roadmap for the portal you already have. Every dollar of it is credited if we go on to do the work.
Marketplace connectors $2.5k each, custom integrations $10k each. Then a named team with SLAs to keep the portal matched to a changing go-to-market.
Work out your own figure before you talk to anyone.
Three situations where we will tell you so on the first call.
Yes, if the model is account-first. Product events land on the company record, qualification runs in its own pipeline, and deals are created only when written criteria are met. Fiverr's Pro and Enterprise businesses run in one portal today.
Through an integration from your product database, billing system or analytics tool. A marketplace connector is $2.5k; a custom integration that maps your events to HubSpot properties and timeline events is $10k. We scope which events matter first, because most of them do not.
Yes, and that is the point of connecting the analytics tool. Usage events from Amplitude, Mixpanel or Segment become properties and timeline events on the contact and company, so segments, email nurture and lead scoring key off what people did in the product, not what they downloaded. The same signals trigger a Slack alert or a task to the AE or CSM when an account crosses a line you have defined, and the handoff runs on written criteria rather than a hunch.
Yes. We merged Fiverr's two instances into one without disrupting active sales, then reshaped workflows, automations and the integrated stack around the single portal.
A separate qualification pipeline owned by sales development, with mandatory fields and handoff criteria before a deal can exist. That is what restored forecast credibility for the AI platform provider in the story above.
From $40k for one hub, starting fresh. Leaving a legacy system adds a flat $25k however many systems you leave, so the smallest migration is $65k. Each further hub is $25k, and the migration calculator prices your exact stack. Connectors are $2.5k, custom integrations $10k, and ongoing support $4k to $9k a month.
Work out what the build costs for your stack first. When you want it checked against your actual motions, tools and team, that is what the call is for.
+972-54-819-1655
info@penguinstrategies.com
4 Dolev Street, Ra'anana, Israel
