Business Analyst – ERP / Complex Business Systems

Remote / Work From Home – Australia SaaSplications

A BA role with depth, variety and long-term customer relationships

SaaSplications is looking for an experienced Business Analyst to join a small, established software team working with a broad and deep business platform used across multiple industries. This is an unusual BA opportunity for someone who enjoys both variety and depth.

We have close, ongoing relationships with our customers and often work much more like an extension of their internal team than a traditional software supplier.

You might be helping one customer improve an employee or training process, another rethink inventory or purchasing, and another design a completely different operational workflow.

Over time, you get to understand not only our software, but how a range of different businesses actually work.

As you develop that knowledge, we want you to become someone our customers trust to help them think through changes to their businesses.

You get the depth that comes from working with the same customers and platform over many years, while still enjoying the variety of working across different businesses and industries.

About us

Our core team has worked together for around 10 years. We have highly experienced and capable developers and testers, a substantial existing platform and long-standing customer relationships.

Our platform is multi-tenanted and supports customers across different industries. It is both broad and deep, with many interconnected business processes.

We don't believe every customer should be forced into a generic industry workflow.

We work closely with customers to understand how they want their business to operate and extend our platform to support those processes.

At the same time, because we have a multi-tenanted platform, a requirement that begins with one customer often causes us to consider whether the underlying capability could be designed flexibly enough to benefit other customers as well.

That balance is an important part of our solution design:

Meet the customer's real business need without unnecessarily limiting the solution to one customer or one way of working.

Why we're hiring

We want to improve the work that happens before development starts. Where we currently lose time is when a requirement hasn't been worked through sufficiently end-to-end with the customer before it reaches development.

The initial requirement may appear transparent, but questions, exceptions or alternative scenarios can emerge once the customer sees the developed solution. That results in changes and avoidable development rework.

We want an experienced BA to help us move more of that thinking forward.

The objective is to reach a point where the proposed solution has been properly investigated, made tangible through flows and designs, challenged internally, understood by the customer and approved by both the customer and our development team before the build starts.

Understanding context is important

Our relationship with a customer doesn't end when a project is delivered. Their businesses evolve. Processes change, new services are introduced, personnel change and new requirements emerge.

It is therefore very common for us to extend or modify functionality that we previously designed and built with a customer.

You won't be starting from a blank sheet each time.

Before designing a change, you will need to understand:

- how the customer currently operates;
- what we have previously built with them;
- why the existing process was designed that way;
- what has now changed;
- how the customer is actually using the system;
- what existing functionality can be reused or extended;
- what other parts of their business or our system may be affected; and
- whether the requirement has implications or opportunities across our wider customer base.

To help you do this, you will have access to relevant source code, Confluence documentation, existing screens, Figma designs, diagrams, process flows and the knowledge of our experienced team. You don't need to be a developer, but you should be comfortable investigating an existing complex system and working closely with technical people.

What you will do

You will take requirements that may initially be incomplete and work with the customer and our team to turn them into considered, developer-ready solutions. Depending on the requirement,



your work may include:

- customer discovery and requirements discussions;
- understanding existing business processes;
- investigating current system functionality;
- reviewing relevant existing code and documentation;
- identifying missing requirements, assumptions and edge cases;
- considering system and business impacts;
- designing process and user flows;
- creating Figma wireframes and screen designs;
- defining business rules, validations and permissions;
- considering how a solution should work across our multi-tenanted platform;
- documenting exceptions and alternative scenarios;
- developing acceptance criteria;
- developing sample end-to-end testing flows as part of the design;
- taking the design through customer and developer review;
- refining the solution following that review; and
- helping maintain the associated help and training documentation.

We don't want documentation for documentation's sake. The objective is to make the proposed solution sufficiently tangible and considered that the customer can say:

“Yes, this is how we need it to work.”

And our developers can say:

“Yes, this works with the wider system and is ready to build.”

Rigorous review is part of our process

Our developers have worked with the platform for many years and have deep knowledge of its architecture and the ways different parts of the system interact. We want the BA to take advantage of that knowledge.

Developer review is part of solution design, not simply a handover after the design is finished.

You should expect your proposed solution to be challenged.

A developer may question an assumption, identify existing functionality you weren't aware of, point out an impact elsewhere in the platform or suggest a simpler or more flexible approach.

We consider this valuable.

We are looking for someone who actively welcomes rigorous review, is comfortable explaining their reasoning and is equally comfortable changing a design when the review identifies a better solution.

The goal isn't to defend the first design.

The goal is for experienced people with different perspectives to challenge it until we collectively have confidence in the solution.

Our process is broadly

Understand → Investigate → Design → Review → Refine → Agree testing flows → Customer & developer approval → Build → Test → Document & train

AI is an important part of how we want to work

We are enthusiastic users of AI and believe it can significantly accelerate good business analysis and solution design. We would particularly like someone who already uses tools such as ChatGPT, Claude, Codex or similar as part of their work.

You will be encouraged to use AI to help:

- investigate existing source code and functionality;
- bring together information from code, documentation, diagrams and screens;
- identify gaps, questions and edge cases;
- explore alternative solutions;
- create and critique workflows;
- accelerate Figma wireframing and prototyping;
- develop requirements and acceptance criteria;
- identify system impacts; and
- develop comprehensive testing scenarios.

We aren't interested in producing AI-generated documentation simply because it can be produced quickly. The end result must be considered, accurate and usable.

We see AI as a way to investigate more thoroughly, explore more possibilities and produce better designs in less time.

Help documentation is part of the solution

Our customer and internal help documentation is currently maintained in Atlassian Confluence, and helping us maintain and improve it will be an important part of this role. Because we build functionality around the particular processes our customers want to operate, good documentation is especially important.

The people involved in designing a feature today may not be the people using it several years from now.

When customer personnel change, knowledge can be lost. Customers can stop using valuable functionality they previously requested simply because new personnel don't know why it exists,



what it can do or how it should be used.

Good documentation therefore protects our customer's investment in the solution and our investment in developing it.

As you work with the system, you will help us:

- identify missing, unclear or outdated documentation;
- maintain existing Confluence help material as functionality evolves;
- document new functionality;
- create useful training material;
- use screenshots, diagrams and examples where appropriate;
- explain not only what functionality does, but where appropriate when, why and how to use it; and
- improve the quality and organisation of our knowledge base over time.

A successful change should leave us with more than working software. It should leave the customer and our team with a lasting understanding of what was built, why it exists, how it fits into the business process and how to use it effectively.

About you

We expect you will have substantial experience as a Business Analyst, Business Systems Analyst or Functional Analyst working with complex business software. Experience extending an existing ERP, SaaS platform or other broad integrated business system would be particularly valuable.

You are likely to enjoy this role if you:

- genuinely enjoy understanding how different businesses operate;
- like building long-term relationships with customers;
- enjoy variety and learning about different industries;
- can turn an initially incomplete requirement into a considered solution;
- naturally investigate existing functionality before designing something new;
- think about the wider business and system impacts of a change;
- can move comfortably between customer conversations and technical discussions;
- enjoy making ideas tangible through process flows, diagrams and Figma;
- think about testing while designing, rather than after development;
- actively seek constructive feedback on your work;
- are comfortable having experienced developers challenge your design;
- are willing to change your approach when someone identifies a better solution;
- are interested in using AI extensively to improve the quality and speed of your work; and
- are comfortable working independently from home as part of a small, experienced team.

You don't need to know our system or our customers on day one. A significant part of the opportunity is building that knowledge over time and becoming a trusted member of the wider team supporting each customer's business.

Applying

Please send us your CV together with a short introduction. We'd particularly like to hear about:

1. A complex ERP or business system you have worked with and the kinds of changes you helped design.
2. How you take an initial customer request through to something ready for development.
3. An example where feedback from a developer, customer or other specialist significantly changed or improved something you had designed.
4. An example where understanding the existing system or wider business process changed the solution you initially expected to build.
5. How you currently use AI in your BA or solution-design work.
6. Your experience with Figma, process diagrams, wireframes and help or training documentation.

You don't need to write an essay. Specific examples are much more useful to us than formal responses.

Our recruitment process

We don't want applicants spending hours completing unpaid exercises. We'll initially review your CV and responses above and speak with applicants whose experience appears to fit what we're looking for.

That initial conversation will focus on work you've actually done: the systems you've worked with, how you approach requirements and solution design, how you work with customers and developers, and how you use AI.

A smaller number of candidates will then progress to a more detailed discussion.

Only a few shortlisted candidates will be invited to undertake a paid practical exercise based on the type of work we actually do.

You will be encouraged to use AI and your normal tools.

The exercise won't only be about the first design you produce. We will review it with you, challenge some of the assumptions and provide additional information — just as our developers and customers will in the role.

We will be interested in how you respond to that review and how the solution improves as a result.

It should give us a good understanding of how you work — and give you a realistic view of what it would be like to work with us.

📌 Business Analyst (Sydney)
🏢 Saasplications
📍 Sydney