The Rossera Way

A delivery methodology. Built around one team.

The Rossera Way is our delivery methodology for bringing business analysts, engineers, client SMEs and IT together from discovery through to adoption, working continuously, learning quickly and building client ownership as we go.

Business + engineering together Prototype while requirements evolve Client capability built in delivery AI removes delivery overhead
Talk to Rossera Learn more
Live business problem

One outcome.
One team.

Focused on the same operational problem.

Understand Prototype Validate Refine
Delivery role

Business Analyst

Works directly with users and SMEs to understand the operational problem and translate it into a clear delivery backlog.

Problem → process → outcomes → backlog
AI-enabled delivery

AI keeps documentation and technical knowledge current while the team stays focused on solving the business problem.

How we actually deliver

The people shaping the solution are the people building it.

Instead of separating discovery, design and build into different teams, Rossera keeps business analysis and engineering in one continuous delivery cycle with your people.

Client business Real process knowledge, priorities and validation
Rossera Business Analyst

Stay close to the problem.

Understand how people actually work, identify friction and translate outcomes into a backlog the team can act on now.

Understand → shape → prioritise
Rossera Engineer / Configurator

Make the idea tangible.

Prototype, configure and integrate while requirements are still evolving, so discussion happens around something real.

Prototype → configure → improve
Client IT Architecture, security, integration and operational fit
The team works in one continuous loop. Not a chain of hand-offs.
Understand

Work directly with users and the real process.

Make

Turn the emerging requirement into something tangible.

Validate

Put it back in front of the people who will use it.

Improve

Feed what the team learns straight back into delivery.

AI-enabled

AI supports the team by removing repetitive documentation and knowledge-maintenance work, keeping delivery information current as the solution changes.

Process documentation Technical knowledge
Less time translating between teams. More time solving the problem together.

Client business and IT remain part of the working team throughout, so context, ownership and capability are built into delivery rather than transferred at the end.

The people behind the Rossera Way

A focused team stays close to the problem from start to finish.

The Rossera Way is built around a small joint delivery team rather than a chain of hand-offs. Business analysts, engineers, client subject-matter experts and client IT work together throughout delivery, with specialist support brought in when it adds value.

Rossera Business Analyst

Keep the work anchored in the business problem.

The Business Analyst works closely with users and subject-matter experts to understand the current process, uncover pain points, shape the future state and translate business outcomes into clear stories, priorities and acceptance criteria.

Rossera Engineer / Configurator

Turn understanding into something people can use.

Engineers and configurators stay close to the discussion rather than receiving requirements through a hand-off. They prototype, configure, integrate and refine working solutions alongside the analyst and client team.

Client Subject-Matter Experts

Bring the reality of the process into every decision.

Client SMEs contribute the operational knowledge that cannot be captured in a requirements document alone. They explain how the process really works, test assumptions and validate whether each iteration solves the right problem.

Client IT

Make sure the solution fits the wider environment.

Client IT stays involved in architecture, security, data, integration and operational decisions. This keeps delivery aligned to the organisation's technology landscape and helps build the capability to support what is delivered.

Specialists when needed

The core team stays deliberately small. Rossera specialists in architecture, data, integration, AI, security or product engineering join when the problem requires them, then step back when their expertise is no longer needed. The aim is to add capability without creating unnecessary layers.

How the team participates 01 Engage 02 Design 03 Create 04 Refine 05 Validate 06 Adopt 07 Learn
Business Analyst
Engineer / Configurator
Client SME
Client IT
Rossera Specialists
AI in delivery

Less administration. More time solving the process.

AI is already part of how Rossera keeps process documentation and technical knowledge current as delivery moves.

Configuration Workbook Generator

One click. A documented process.

Generate comprehensive documentation directly from the configured process, then generate it again as the process evolves.

Real DEMO_PAYREQ example Configurator · RPS 05.03.01 Added August 2026
DEMO_PAYREQ_overview.html
ProcessSense

Payment Request

Self-service payment requests demo

Code: DEMO_PAYREQ Nodes: 5 ● Active
Contents
Process nodes
Regions
Process Flow

Payment Request

Select a process node to inspect the generated configuration.

Generated
Payment Request
↓
↓
↓
↓
↓
Process Node

Prepare Invoice

DEMO_PAYREQ_CREATE

Prepare Invoice
DEMO_PAYREQ_CREATE
Page · User Input Start Node
Outcome Type Next Node
Submit USER_INPUT Grant Owner Approval
Process Node

Budget Owner Approval

DEMO_PAYREQ_APPROVE

Outcome Next Node
Reject End Process
Approve Upload Invoices / Supplier Team
Return Enter Grant Payments
Timeout Create Service Request
Region

Payment Information

Prepare Invoice · 11 attributes

Supplier Type VALUELIST
Invoice Approver VALUELIST
Supplier Required
Payment Date Required
Description Required
Region

Invoice Lines

Prepare Invoice · 10 attributes

Business Unit VALUELIST
Cost Centre VALUELIST
Net Amount NUMBER
Tax NUMBER · Read-only
Total Amount NUMBER · Read-only
Expressions

Process logic

3 unique expressions · 0 data sources

SUM.DEMO_PAYREQ_PAYMENTS.DEMO_PAYREQ_GROSS_AMOUNT gt DEMO_PAYREQ_INFO.GRANT_DEMO_AMOUNT
DEMO_PAYREQ_AMOUNT() != null && DEMO_PAYREQ_TAX_RATE() != null
DEMO_PAYREQ_AMOUNT() != null && DEMO_PAYREQ_TAX_AMOUNT() != null
Change the live process configuration Generate again → documentation stays current
Rossera Wiki

Keep product knowledge as current as the code.

When ProcessSense changes, Claude Code helps turn the source behind those changes into structured technical documentation for Rossera's central Product Development knowledge base.

01
Product development

A feature is built.

The developer provides the newly written ProcessSense code. The source itself becomes the starting point for the documentation.

PaymentApprovalService 
function validatePayment(request) {
  if (request.total > request.limit) {
    return {
      status: "approval_required",
      owner: request.budgetOwner
    };
  }
}
Claude Code

Helps interpret the source and document what the feature does, how it behaves and how it connects to the wider product.

02
Rossera Wiki

The knowledge is captured.

Technical detail becomes structured documentation that lives in one central ProcessSense knowledge base.

ProcessSense Knowledge Base Payment Approval Logic
Updated from source
Feature overview

Determines whether a payment requires additional approval based on its configured limit.

Technical behaviour

Requests above the limit are routed to the configured budget owner before the process continues.

Related areas
Payment Request Budget Owner Approval Routing
03
Future development

The next developer can find the answer.

Instead of relying on the person who originally built the feature, another developer can quickly understand the logic before changing or extending it.

Search: payment approval logic
↗
ProcessSense · Technical documentation Payment Approval Logic

Understand routing behaviour, dependencies and the underlying implementation before making a change.

Why it matters
Product knowledge evolves with ProcessSense instead of getting left behind as the product changes.
Less manual documentation Faster onboarding for future developers Less reliance on individual team knowledge A central, maintainable ProcessSense knowledge base
How we work together

Not client and supplier. One delivery team.

The Rossera Way deliberately creates a collaborative environment involving both business and IT throughout delivery. We adapt to the client's culture, organisational structure and internal ways of working while maintaining clear governance and accountability.

The objective is to create an environment where business users remain engaged and client teams develop genuine ownership of the solution.

Rossera

Methodology, product expertise, delivery experience and coaching.

Client business

Process knowledge, priorities, validation and acceptance.

Client IT

Architecture, integration, security and operational fit.

One delivery team Same backlog, same ceremonies, same definition of done.

Shared ownership

Delivery decisions are made together.

Open governance

Risks, issues, decisions and priorities remain visible.

Business + IT together

Business experience and technical expertise are brought into the same delivery cycle.

Cultural alignment

The delivery model adapts to the client environment rather than forcing an artificial operating model onto the organisation.

The Rossera Way

Better processes. Built together.

The Rossera Way brings your people and ours into one delivery team, working closely around the problem, learning through working solutions and building the capability to keep improving after delivery.

Talk to our team Explore the platform