Clear scope. Practical pricing. No mystery project.
What actually drives the cost of an automation, integration or software project, and the shapes a project with 23Labs can take.
What drives project cost
The same factors apply whether the project is a small automation or a larger build.
APIs and software access
Whether the systems involved have an API or connector, and whether we can get the access a project needs.
Number of systems
Connecting two systems is a smaller project than connecting five, even if each individual connection is simple.
Workflow exceptions
The straightforward path is usually quick to automate. The exceptions, the edge cases and the judgement calls, are where scope grows.
Data quality
Clean, consistent data moves faster. Messy or inconsistent data usually means extra work to normalise it first.
Security requirements
Specific access controls, data handling rules or approval processes add real scope, and we price that scope rather than skip it.
Custom interface
A dashboard, portal or internal tool is more work than an automation that runs quietly in the background.
Implementation support
Testing against real examples, handover and training are part of a project, not an afterthought.
Ongoing support
Keeping a system reliable as your business changes is separate, ongoing work, priced separately from the initial build.
Three shapes a project can take
No fixed packages. We scope the shape that fits the problem.
Focused automation or integration
A specific, repeatable step, or a connection between two systems. Usually the fastest path to a working result, and often the right starting point.
Custom software build
An internal tool, dashboard or portal, built when the process needs a place to live that off-the-shelf software doesn't provide.
Ongoing support and improvement
Keeping automations, integrations and software reliable as your systems, team and processes change after the initial project.
Want a rough sense of what a repetitive task is costing your team before you ask for a quote? Try the automation savings calculator.
Pricing questions
Can we start small?
Yes. Most projects start with the highest-value, most repeatable step rather than a complete system. A smaller first project also tells us how well a larger one would work.
Is the discovery conversation paid?
The initial conversation to understand your process and systems is not a paid engagement. If a project needs a more detailed scoping phase before a fixed quote can be given, we'll say so and agree that separately.
What's in a scoped proposal?
The specific process or integration in scope, the systems involved, what we'll build, what's excluded, and the cost and timeframe for that defined piece of work.
What does a project typically cost?
Custom software and automation projects typically start from A$2,500. Final pricing depends on the systems involved, complexity and scope. For a larger or more complex project, book an initial consultation. We don't publish retainer pricing or package tiers here, because the right shape and cost depends on what you're actually trying to solve.
Do you charge differently for ongoing support?
Ongoing support is scoped separately from the initial build, since it covers different work: keeping systems reliable as things change, rather than building something new.
Ready for a practical estimate?
Tell us what you're trying to solve and which systems are involved. We'll scope it and come back with a proposal.