GTM Engineer (Revenue Operations) | Own the HubSpot spine at an AgTech company growing 40 percent a year | Melbourne, four days in Richmond Most RevOps roles hand you someone else's mess and ask you to keep it running.
This one asks you to redesign it.
Onside is AgTech software protecting the world's food supply.
Farms, agribusinesses, contractors and processors use it to know who is on-site, track movement across properties, and manage biosecurity and safety risk at enterprise scale.
Every check-in builds a record that didn't exist before, and the network it connects gets more valuable every day.
Founded in Canterbury, New Zealand in ****.
Now across New Zealand, Australia and the UK, with the US next.
About 45 people, growing roughly 40 percent year on year.
Ranked 38th on the Deloitte Fast 50 in **** and named to the Forbes Asia 100 to Watch the same year.
More than 9,000 agribusiness operations on the platform, including McCain, Yalumba, Treasury Wine Estates and Inghams.
Over 4.4 million digital check-ins.
22,500 properties mapped.
Product and engineering sit in Christchurch.
The Melbourne team is the entire commercial side of the business: sales, customer success and marketing.
This is a new, dedicated role reporting to the Head of Revenue.
The systems are in place and running.
What the business hasn't had until now is one person who owns the architecture end to end and gets to decide how it should be designed.
It is a build role rather than an advisory one.
Onside have no shortage of people who can say what the company should do.
What they need is the person who takes it away, ships it, and comes back with what the results say.
Why this role First dedicated RevOps hire, reporting to the Head of Revenue, with the architecture yours to define rather than inherit and maintain An AgTech business with real commercial traction: 9,000 plus operations, enterprise logos, two consecutive years as the fastest growing tech company in Canterbury HubSpot is the spine and stays.
Most of the rest of the stack is genuinely open to you Priorities are already clear at leadership level, so you are not spending your first quarter arguing that the work matters Genuine tooling freedom.
The commercial team is well resourced, and new tools get adopted quickly where the return is clear AI-agnostic and actively encouraged.
Claude and Claude Code are already in use across the business, including in engineering Broad scope across Sales, Customer Success, Marketing and Partners,



so you see the whole funnel rather than one segment of it A technical counterpart in the business.
The product team and the data scientists in Christchurch work with you on this, and they enjoy it as much as you do What you'll actually do Own HubSpot end to end.
Pipelines, lifecycle stages, the data model and the taxonomy across Marketing, Sales, Partners and Customer Audit the go-to-market stack, decide what it should look like, and then be the person who builds it Build forecasting and revenue intelligence solid enough to commit a quarter against Automate the commercial funnel.
Lead routing, scoring, enrichment, handoffs, and contracting and proposal workflows Make one process run end to end from marketing through to support, with alerts when something stalls and reporting that explains what is stuck and why Make the deal qualification framework live inside the CRM rather than in a slide deck, so the sales team can see what happens next at every stage Wire Marketing, Sales and Customer around one coordinated account experience, and turn product usage data into signals for expansion and retention Connect systems that were never designed to talk.
HubSpot at the centre, with ChargeBee for billing, Traction for customer success, Cradle for calling and Pendo for product analytics, plus whatever comes next Evaluate, integrate and retire tools across the GTM stack, and keep the data clean between them Help size markets and design territories as the business moves into new segments and new countries Set the reporting the commercial team runs on, so there is one version of the numbers Who this suits You don't need an AgTech background.
What matters is whether you build things yourself, and whether you have owned a CRM's architecture or only ever worked inside one someone else designed.
Real HubSpot depth.
Not administration.
Architecture Fluent in automation and APIs, whether that is Make, Zapier, n8n or working directly against the API You think in data.
You can model it, clean it, forecast on it, and tell when a number is lying You have removed manual work before and made a team measurably faster, with the numbers to show it You teach yourself.




Something you have never touched lands on your desk on Thursday, and by Monday you have worked it out and built it, because you wanted to Self-driven, low ego, and you would rather hear feedback plainly than politely You do not need to have done all of this before.
The tooling in this space turns over quickly enough that someone current to a system can be as effective in it as someone who has used it for years.
Some track record matters, the full set doesn't.
A SaaS or tech background matters more here than agriculture.
Onside hire technical capability and teach ag.
If you happen to speak farmer as well, that puts you close to ideal.
What success looks like First 30 days: you have audited what exists and you have a clear point of view on what the stack should be and how it gets rolled out By 60 days: the majority of it is built By 120 days: you are showing the business what is working and the results behind it Beyond that: forecasting is trusted, HubSpot is one clean source of truth, manual work is measurably down, and the stack is consolidated and talking to itself The pace is deliberate.
The expectation is that modern tooling lets you build quickly, and that you would rather ship than plan.
Where this goes This is not a project with an end date.
Once the foundations are in, the scope grows as the business expands internationally, and into commercial segments that don't have a motion built yet.
This is the first seat in a function that will get bigger, and the person in it will have the strongest claim on leading it.
Why this opportunity is different Worth being straight about the hard parts.
Four days a week in the Richmond office is not flexible, and you should treat it as fixed.
The brief is broad: deep HubSpot, forecasting, automation and ABX in one person is genuinely demanding, and there is no team beneath you today.
Feedback at Onside is blunt by design.
Not everyone enjoys that, and if you don't want to get better you won't last.
What you get in return is unusual.
Most RevOps seats sit three layers from the decision, waiting on approval for a tool that costs less than a laptop.
This one reports to the Head of Revenue in a 45-person business, and the architecture is yours to set rather than defend.
The work already has a clear mandate behind it, so you are not spending your first six months convincing anyone it matters.
Apply now, or reach out to Hugo Bieber for a proper conversation about the role and the business before you commit to a process.

📌 Gtm Engineer - Onside (Victoria)
🏢 Pointer Strategy
📍 Victoria