The short version
Platforms that fit, and less manual work.
Data models that fit
Custom objects, fields and associations in HubSpot and Salesforce, tables and records in NetSuite or Business Central — modeled against how the business actually works.
Portals for the people outside
Customers and partners need a way in that isn’t an email to someone’s inbox. A portal reads from your ERP and CRM and shows exactly what it should, nothing else.
Workflow automation
The steps currently held together by someone remembering: approvals, hand-offs and the messages that go out when a record moves — in the CRM, in the ERP, or across both.
Quote to cash
The whole path, from the first quote in the CRM to the invoice in the ERP that closes it.
Client portals
Order status, invoices and requests, straight from the ERP, without a license for every customer.
Approval flows
Who signs off, in what order, and what happens when they’re on vacation.
New pages and apps
A new page in Business Central, a UI extension in HubSpot, a component in Salesforce — so the tool people already have open is the tool they use.
Partner portals
Deal registration and a shared pipeline, with the boundaries actually enforced.
Transactional email
The messages a record triggers, sent from infrastructure that stays out of spam.
Platforms that fit
Your ERP and CRM hold the business as it is, so the spreadsheets beside them stop being necessary.
Less manual work
The steps that were a person copying between two screens become steps that happen on their own.
Grove is not an ERP or CRM implementation, and not marketing setup, campaign management or admin training — there are better people for those, and we’ll point you to them.
Is this different from system integration?
Yes. Integration moves data between systems; customization changes what one system can do — a new page, a better data model, an automated approval. Most projects need a bit of both, and one quote covers them.
Does this lock us further into the platform?
Less than the alternative. Custom objects and fields live in the platform’s own model, so they work natively.
Where a piece of logic is genuinely portable, we build it outside the platform on purpose, so a future migration moves it rather than rewrites it.
Can our own admin maintain it afterward?
That’s the intention, and it shapes what gets built. Native configuration is preferred over code every time, and whatever has to be code is handed over documented.
Which platforms?
HubSpot and Salesforce on the CRM side; NetSuite, Business Central and the other ERPs we integrate on the ERP side.
A platform that almost fits the way you work?
Tell us which platform you run and where it stops fitting the way you work. Datsugi replies within 2 business hours, guaranteed (CET).
Arrigo Lupori
Founder & Managing Director