Built for the people running
the job.
Two to five projects. No time.
No surprises.
You're running programme, RFIs, client comms, sub coordination, and the second-stage approval on every claim. You don't want to look stupid in front of the superintendent because a drawing scope gap became a variation on site. Deep Space gives you the project view that doesn't lie, with the commercial implication of every programme shift visible from the dashboard, not from a CA's email three days later.
What your day actually looks like
You're paired with a CA on every project. In smaller builders the two roles collapse into you. Either way, you're the one with the client's number in your phone.
You're not the calculation. You're the decision. You read the certification, you approve the variation, you decide whether theprogramme slip becomes a notice to the client or stays in-house.
What you're dealing with
Mid-tier commercial PMs have never had a project platform built for the way two to five jobs actually run. Too lean for the enterprise tools, too senior for the basic ones.
You move the slab pour by two weeks. The follow-on trades are fine, but the cashflow profile just changed and Finance won't know until end of month. By then the PM on the next job has made the same call.
You raised the RFI six weeks ago. The consultant's response is in someone's outbox. The sub is on site asking about it now. You're scrolling through three months of email to find the wording.
The super said 'just do it' in a meeting. There's no paper. Three months later, the variation is rejected because the contract requires a written notice within seven days. The work happened anyway. The money is gone.
The CA certifies. You're supposed to approve. The claim is at the client before you've seen it. The next time you talk to the CA, they're already preparing the next claim.
"I just want the software to flag the scope gap before I push the RFI, so I'm not the one who looks like they didn't read the drawings."
How Deep Space helps Project Managers
Programme connected to commercial. RFIs linked to drawings. Variations tracked from the moment the super opens their mouth. Every project, one view.
Programme
Live construction programme connected to commercial and delivery. Schedule shifts flag commercial impact automatically, not three days later via email.
Master programme with milestone and package tracking- Rolling 1, 2, 4-week look-ahead for trade coordination
- Programme shifts flag commercial impact against the cost-to-complete
- Collaborative editing, ingested from MS Project, no viewer-only restriction
- Subcontractor portal access for package milestone updates
MS Project disconnected from cost, the look-ahead rebuilt in Excel every Monday, the email to Finance asking what a two-week slip means.
Delivery: RFIs, Site Instructions, Defects
One register for everything that happens between you and the design team. The drawing the RFI relates to is attached. The consultant can't say they didn't see it.
- RFI register with drawing links, response tracking, and status
- Site instructions issued and tracked from one place, with the contractual notice timing flagged
- Defect register with sub assignment and close-out
- RFIs flow into the variation register when they generate a cost impact
- Subcontractor portals so each trade sees only what affects them
RFI registers in Excel, site instructions via email, defect lists in spreadsheets or PDF markups, the consultant who 'never received' the RFI.
Head Contract Progress Claims and Variations
You approve the claim after the CA certifies. You sign off on variations above the threshold. The whole trail sits on one record.
- Two-stage approval: CA certifies, PM approves, then the claim goes
- Variations from client instruction through to claim, with notice timing tracked
- EOT tracking with the contractual basis attached
- Claim history exportable to defend a final account dispute
- Approval routing configured to your project thresholds
Claims that get sent before the PM sees them, the variation register that lives in three places, the EOT defended six months late.
Correspondence
Every client letter, instruction, and response timestamped. The paper trail builds itself. When the contract goes to dispute, you have the evidence pack.
- Inbound and outbound correspondence logged against the project
- Contract-driven notice timing flagged automatically
- Cross-references to the RFI, variation, or claim the correspondence relates to
- Search across the full project history
- Audit-ready export for dispute response
Outlook as the contract paper trail, the question 'what did the super say in that meeting' with no good answer.
Action Engine
What's open. What's overdue. What's on the critical path. One view, every morning.
- Cross-project action list ranked by overdue and critical-path
- Actions assigned to subs, consultants, or internal team members
- Status updates pulled from the live workflow, not from email
- Escalation paths configured per action type
- Filter by project, by trade, by responsible party
Monday morning meeting notes that nobody reads, the action list in a notebook, the chase email that goes unanswered.
%20(1).png)
.png)
Used by PMs running two to five jobs at a time.
Mid-tier commercial builders. Contracts between half a million and a hundred million. PMs juggling delivery, commercial, and client management on every project.
Project Manager, ANZ mid-tier builder
Senior PM, NZ commercial builder
Project Manager, Auckland
Construction Runs Better Here.
Thirty minutes, no install, no commitment. We'll walk through a workspace with the programme, the RFI register, and the variation register actually running on a project your size.