Associate Implementations Analyst

Lovabo is a Perth tech startup building software for contractors and other operational businesses across mining, engineering, construction, or shipping.

These businesses still run important workflows through disconnected spreadsheets, emails, paper, old systems and manual reconciliations. The workflows might not sound glamorous: purchasing, inventory, movable assets, maintenance handovers, accounting data and the movement of information from field to office. But when they break, the operational and financial consequences are real.

Larger software companies tend to start with their platform. We start beside the customer, work out how the job actually gets done, and build around the missing workflow. Being small and using modern AI-enabled engineering systems means we can sit closer to the problem and move faster.

You’ll sit with customers, investigate how their operations really work, and turn that evidence into requirements an engineer or software agent can build from and a customer can confidently accept.

THE ROLE

You’ll help make sure we build the right product, not simply the first feature someone requests. Your work will shape what we build, how we test it and whether it works when it meets the real world.

This isn’t a narrow role inside an established department. You’ll see customer conversations, product decisions, implementation, testing and commercial reality in the same week. You’ll help establish how Lovabo takes operational problems from discovery through to working software.

WHAT YOU’LL DO

Responsibilities will grow as your judgement and capability develop. You can expect to:

• Prepare for and join onsite workflow sessions with operators, managers and system owners.
• Ask customers to show you recent transactions, exceptions and workarounds rather than describing the ideal process.
• Map workflows across people, systems, data, decisions, physical operations and handovers.
• Identify systems of record, manual workarounds, reconciliation points, failure states and conflicting stakeholder priorities.
• Separate what was stated, what was observed, what has been assumed and what remains unknown.
• Turn customer evidence into clear problem statements, business rules, data rules, requirements, exclusions, acceptance criteria and open questions.
• Trace how an operational fact moves between spreadsheets, exports, databases, APIs and financial or operational systems.
• Develop test scenarios, support acceptance testing and record what passed, what failed and what remains unresolved.
• Support data mapping, implementation documentation, customer training, handover and adoption.

WHAT YOU’LL NEED TO UNDERSTAND

You don't need to arrive knowing every business’s workflows or every incumbent system. You do need enough business-systems literacy or the interest to follow a consequential customer conversation and ask a useful question.

The work touches:

• requisitions, approvals, purchase orders, partial receipts and backorders;
• inventory receipt, location, issue, transfer and stocktake;
• durable assets moving between projects, jobs and sites;
• the gap between destination intent, physical custody, actual consumption and financial value;
• invoices, journals, GL accounts, cost centres and reconciliations;
• operational versus financial systems of record, audit trails, corrections and approval authority;
• migrating off older systems without breaking the workflow people rely on.

WHAT WE ARE LOOKING FOR

Around two to four years of relevant experience, or just super high agency with a deep interest in solving problems in not so boujee industries.

Beyond that:

• You listen well enough that operators show you how work really happens.
• Your follow-up questions expose exceptions, ambiguity and who actually decides.
• You think in systems: people, data, software, controls and physical operations, and how they pull on each other.
• You write clearly, without jargon, and can state what's known, what's assumed and what's still open.
• You can facilitate a customer conversation without performing certainty, and take direct feedback well enough to make the second pass materially better.
• You trace claims back to source evidence, and you'll say "not yet" when the evidence is weak.
• You're curious about drilling, mining and industrial operations, and careful with customer data, production systems and commercial boundaries.

YOU’LL PROBABLY DO WELL IF

• You listen closely enough that people show you how the work really happens.
• Your follow-up questions uncover exceptions, ambiguity and who actually has authority.
• You think in systems: people, data, software, controls and physical operations.
• You can follow a claim back to its source rather than relying on a confident explanation.
• You write clearly and can distinguish facts, assumptions and unknowns.
• You’re comfortable with spreadsheets and structured data, and interested in databases, SQL, APIs and data mapping.
• You can take direct feedback and make the second version materially better.
• You’re excited by the idea of helping build a company, not only performing a predefined job inside one.

You must have the right to work in Australia and be able to spend meaningful time working with me and customers in Perth.

HOW WE’LL WORK TOGETHER

Lovabo is early. There aren’t layers of management, a completed playbook or a narrow box waiting for you to occupy. You’ll help create the way we work.

A few things that are important to me:

• Start with the real problem. Don’t accept the first request as the whole answer.
• Think from first principles. Break the problem down before reaching for a familiar solution.
• Create, test and evolve. The first version teaches us something. Use that evidence to improve it.
• Care about the customer and the craft. Useful software requires both.
• Find a way without inventing certainty. Make progress, surface what you don’t know and escalate before an assumption becomes a promise.
• Focus ruthlessly. A small team wins by solving the important problem, not by appearing busy.

Lovabo is early. There aren’t layers of management, a completed playbook or a narrow box waiting for you to occupy. You’ll help create the way we work and build software experiences for people with tender loving care.