Your business.
Your workflows.
Finally running on one platform you always wanted.
Everything you need to get you started
on a better way to build.
Four simple steps. Structured around your business. Paced around live work.
We walk through what to pull together beforehand and sort the IT side early. The more context you give us, the faster your workspace reflects your business.
with your team
live or sandbox
Your workspace is seeded with your data before we arrive. By the time we leave, your team has navigated their own drawings, cost codes, notices, and site forms.
Hands-on means your team is in the platform throughout. By the time the on-site sessions wrap, your people have done the work themselves rather than watching someone else do it.
One nominated project (live or sandbox) is active in Deep Space before we leave. Your champion team knows the platform. The wider rollout follows from there.
An orientation for your champion team, not a company-wide rollout. Your team works through every delivery and site module on your own project data, building the familiarity that drives adoption.
Your QS, estimators, contract admins, and directors come in for this component. We follow the natural sequence of how you actually run a project, from the first opportunity through to getting paid. Nothing out of order. Nothing that doesn't make sense in the room.
The on-site sessions get you started. What follows is where Deep Space becomes yours. Your dedicated Deep Space implementation lead works through the configuration phase with you. Site forms built to your workflows, approval chains set the way you run them, commercial templates structured for how you price and claim, access configured by role across your team. The platform reflects your business, not a template.
Xero integration established and tested. Your accounts inbox connected so approved invoices and claims flow directly, no double entry, no manual reconciliation.
The nominated project from the sessions goes fully live. New projects start in Deep Space from this point. Existing work in your current system runs to completion in parallel with no forced migration, no pressure.
As more of your team comes on, sessions are run by role and paced around live work. Estimators on tendering. QSs and CAs on procurement, claims, and client invoicing. PMs on delivery and project financials. Site managers on HSEQ and DS Site. Each person trained on what they actually use, when they actually need it.
What your implementation includes.
This typically takes 8 to 10 days over 3 to 6 months. This is what every customer gets, regardless of size or where you're coming from.
What makes your implementation work.
The on-site sessions land well when both sides are prepared. This is what moves the needle on your end.
The questions we always get.
Honest answers. No sales spin. If something isn't answered here, email us directly at help@deepspacegroup.ai and we'll come straight back.
Subbies. You can send tender packages and RFQs via a secure link, they price and submit without any account or portal. You can route documents, Site Instructions, and drawing sets through the subcontractor portal. You can have them submit claims through a structured form tied to their schedule of values. Or you can keep doing what you're doing, subbies can still send claims by email and you process them in Deep Space on your end. Most builders use a mix. The tech-savvy subbies go through the portal. The old-school ones keep emailing. Both work.
Consultants. They can access a dedicated portal for documents, drawings, RFIs, and raising Consultant Advice Notices, or you can keep managing it through correspondence and email. The portal makes the audit trail cleaner. Email is what your consultants already know.
Clients. They can have a clean portal view of documents, progress claims, and variations, or you might decide your client relationship works better with a personal touch and a PDF. Some builders love giving clients portal access. Others prefer to keep that boundary.
There is no right answer. We'll walk you through each option during implementation and help you set it up in a way that actually gets used, not just a way that looks good on paper.
Timesheets, it depends on what you're trying to achieve. If you're already using a timesheet app, we can import your CSV output and allocate labour costs against your project budgets. If you don't have a timesheet tool or want something simpler, we can build a basic timesheet form on DS Site that your team completes from their phone on site. Either way, the hours land in Deep Space against the right project and cost code. The right answer depends on your setup, we'll work through it with you.
Payroll, not something we do. Deep Space doesn't process payroll and we won't pretend otherwise. Payroll stays in your payroll system. What Deep Space does is give you visibility of labour costs at the project level, which is a different thing.
Highly configurable. Site forms, inspection templates, induction flows, SWMS, approval workflows, claim templates, cost code structures, user roles and permissions, document folder templates, email correspondence templates, all of this is shaped around your business during the configuration phase. No two Deep Space workspaces look the same because every builder runs differently.
SaaS platform. At the same time, Deep Space is a platform used by builders across Australia and New Zealand. Core workflows (how a PO is raised, how a claim flows through approval, how a drawing is transmittaled) are universal by design. We don't build one-off custom features for individual customers. What we do is take feature requests seriously. If something you need makes sense for the broader platform, we'll build it and everyone benefits. If it's a specific workflow quirk that only applies to your business, we'll find the best way to configure around it within what exists.
In practice, most builders find that configurability covers the vast majority of what they need. The things that feel like custom requests usually turn out to be configuration problems with a clean solution.
.png)




.png)





