How we engage

A fast start and a clean finish.

Three engagement models, two ways to buy, and the same standards on all of them. Here’s how an engagement starts, runs and ends.

01 — Three models

Add capacity, hand us a build, or hand us the problem.

Compare the three models. On smaller screens, scroll sideways; use the arrow keys when the table is focused.

Question	Staff augmentation	Software engineering	AI product development
What you get	Senior engineers who join your team	A defined piece of work, delivered end to end	An idea taken to launch: vision, design and build, with AI where it’s the shortcut
Who directs the work	You do, through your process	We do, against an agreed outcome	We do, against outcomes agreed with you
Where it happens	Your repos, your tools, your ceremonies	Your repos and tools, alongside your team	Your repos and cloud accounts from day one
Best when	You need hands-on engineering or technical leadership within your team	You know the outcome and want it owned	You have the problem, not the brief
How it ends	A planned handover, on all three. You own what we built.

For suitable projects, we can draw on software agencies and collaborators we know personally and have worked with before. Their involvement depends on the scope and agreed arrangement.

02 — Two routes

Buy direct, or through your agency.

Route A

Direct

Talk to us about the work. We agree the model, the people and the start, and you contract with BigPicture Works Pty Ltd.

Discuss the work

Route B

Via a recruitment or procurement agency

Already buy contractors through an agency? Engage us through them. Same people, same standards.

Agency and procurement partners: send us the role and the stack, and we’ll tell you straight whether we’re the right fit.

Send us a role

03 — Ramp-up

Planned before day one, not discovered after it.

Before day one
Set up to start
Role or scope agreed. Access, accounts and environments requested. A first piece of real work chosen.
First days
Prove the path
A walkthrough of your codebase and pipeline, then a first small change taken all the way through it.
From then on
Work at your cadence
Your stand-ups, your board, your definition of done. Progress visible in your tools, not in our reports.

04 — Handover

You own it after.

Handover isn’t a final week. It starts on day one, so nothing leaves when we do.

Decisions written down

In Confluence, or wherever your team documents, as they’re made.

Everything in your repos

Code, infrastructure as code and pipeline config live with you, not with us.

Walkthroughs

Sessions with the people who’ll own the work, before the engagement ends.

No black boxes

No private tooling or accounts your team can’t get into.