AI-powered business operating platform
Nebula answers enquiries, manages inboxes, prepares documents and coordinates delivery. Its AI assistants and business tools share context, so your team spends less time holding everything together.
The sample agreement
Open the reading
Transformer delivery and commissioning
A supply and commissioning agreement between a principal and a provider, eighty pages of promises, dates and money.
From the obligations
The Provider shall complete commissioning by the end of week 36.
The walk begins
Nebula carries accepted requirements, responsibilities and dates from the signed documents into a delivery plan. Your team reviews the plan, then starts from what was agreed.
Reading assurance
You decide what changes the record.
Reading
Nebula brings together responsibilities, dates and amounts from the documents, with the original wording beside each finding.
Week 1The reading becomes the shared record.
Plan
Nebula carries accepted requirements and their sources into the plan. Unresolved or low-confidence readings stay in draft for review.
A requirement with uncertain ownership or a low-confidence reading stays in draft.
Source review
2 readings remain in draft
Supported
4 plan items
Plan items
6
Draft
2
Accepted
4
Plan changes
From information to useful work
Nebula turns information already in the agreement into useful work: a report for the client, a brief for the specialist, a notice ready to review. Spend less time assembling the background and more time doing the work that needs you.
One example: documents to a drawing
Nebula prepares an editable CAD file, not a picture, with the stated equipment and connections laid out for an engineer to review.
You decide the downstream protection not stated in the source.
You see no device, rating, curve or setting in the source, so the drawing leaves this open.
Nebula writes it as a DXF file that opens in your own CAD tools. The worked sheet here is an illustration, not a live run.
Help shape what comes next
Specialist reports, inspection packs, estimates, handover documents: opportunities for new workflows. Tell us which one your team rebuilds every cycle.
Week 3One deliverable needs a specialist.
Nebula prepares a one-page work order from approved requirements and current job details, so a specialist can start with the agreed scope and terms. Bring verified work back into the same delivery plan.
Quotes and offer terms stay private to the organisation. The head project's deadlines do not move.
The subcontract rests only on wording both parties signed.
Nebula reads progress against the plan and each claim against its approval. Progress that stalls, a blocked path, a claim without proof, and hours past the plan arrive as named findings with a suggested next move. Claims, approvals and part-payments keep their history, so you can begin the next conversation with the position in front of you.
Weeks 9 to 14The switchgear slips, the first claim arrives and a response window opens.
Schedule
Nebula shows what needs to finish first, what depends on it, and which delay would move the recorded finish.
Dates come from the dates and durations the documents provide. Work with incomplete dates stays unscheduled.
Money
Nebula records approval and payment against each claim and keeps what is still due open until it is resolved.
Retention is estimated from the rate the documents state. Without a usable rate, there is no figure.
You submit a payment claim, record the schedule and certification, and carry any shortfall forward until it is discharged.
Every position keeps its date, and Nebula moves no money; your later dispute opens on the recorded history.
You import a MYOB sales invoice or supplier bill report as an XLSX or CSV file, then check the preview before you confirm the import.
The engagement’s supplier bill register lists imported bills with the report that stated them where it can be matched, and whether that exact report is still kept.
Deadlines
Every 15 minutes, Nebula checks each sign-off window, reminds the other party as it closes, and serves a final notice.
Unsupported timing stays unknown
When a payment notice has no source-stated calendar response date, Nebula keeps the response-window state UNKNOWN and tells you to check the notice and source document.
A deadline Nebula does not trust sends nothing to the other party.
On the other party’s window to accept or verify your work, Nebula reminds them at half, three quarters and nine tenths of it, and the last is a formal final notice.
A deliverable’s own due date works differently: once it passes, Nebula tells the item’s owner, and a breach follows only after the grace the documents state.
You read the programme ahead through the forward pass, and each approaching bottleneck arrives as a finding for you to act on.
Your deliverable within five days of its deadline with no evidence attached raises its own alert. The pass writes nothing on its own, and every alert names what produced it.
The same pass also reads claimed progress, blocked notes and hours against the plan. A stall, a blocked path, a claim without proof, or hours running past the plan arrives as a finding with a suggested next move. The pass still writes nothing on its own.
A response can harden into a dispute. Your record is ready without drama.
Required notices build from the agreement, with acknowledgement recorded.
A suspension right is exercised from the clause window the agreement states.
A defect notice carries its rectification date and evidence.
Grounds, evidence and outcomes stay on one dispute.
CSV, PDF, Word and ZIP files with audit and proof references.
You serve a formal notice with its reference number, your signature and its proof reference in one act, with the notification outcome recorded beside it.
Whichever surface you serve from, the notice carries the same reference, signature and proof reference.
When an item is contested, you generate a dispute brief that holds the chronology, the agreement analysis, the submitted position and an evidence summary in one document.
The brief is marked as a Nebula reading, for your review, and it never stands as impartial evidence.
Once both parties have signed, you can export the agreed reading and an audit bundle with its audit report, index and available proof bundles.
An insurance pack summarises the current delivery record, parties, item states, active packs and available proof references.
Week 15The slip needs more time, and the scope has grown.
Once a change is accepted, Nebula moves the affected work, budget and programme together.
On the sample agreement
A calendar change uses your own account, your consent for that purpose and your approval of the exact time. Nebula prepares each step, and people decide it.
The effect on price and programme is visible before agreement.
A lodged claim stays the stated position until the response is recorded.
YOUR CONTROLS
Week 17 · A variation arrives
Choose the read, steer another pass, correct the record and confirm consequential work.
These controls do not bypass authority. Scope, cost and time changes still use the authorised change process that applies to you.
Select an available model and scope before a reading begins.
Point the next pass to a clause, risk or missing fact.
Save a correction within your authority. Keep the original words and author.
Review consequential work before it enters the shared record.
Any morningOf everything in motion, a few things need you.
Companion
Nebula prepares a brief for one project or across the portfolio, with the work behind each update a step away.
Nebula
Microsoft 365Identity, Outlook mail and calendar, Teams and selected SharePoint or OneDrive files
Google WorkspaceIdentity, Gmail message headers, calendar, Chat and Drive files
XeroInvoices, payments and time entries
QuickBooks OnlineInvoices, payments and time activity
MYOBSales invoice and supplier bill reports, imported from file
ProcoreProjects, documents, field activity, labour and costs
Oracle AconexDocument revisions and formal correspondenceConnections require setup and permission for the sources you choose. Bring a selected Microsoft 365 file revision into the job, then choose when to read it. Each document keeps its history while it stays in the job: the original and every revision after it, newest first, each downloadable as the exact file it was. On enabled engagements, an assistant connected over MCP can ask about the work or prepare proposals for review, and its questions and proposals leave receipts. The source and the person’s authority stay visible. Agent connection details.
Finished work leaves more than a folder behind. Nebula keeps confirmed outcomes with the business to support its reputation and give the next team a record to build on.
Week 36Commissioning completes. Delivery becomes proof.
Proof
Where configured, Nebula anchors a recorded event on two networks; each record can be checked with its anchor ID.
Anchoring runs where the project configuration enables it. Each record is checked on its own anchor ID.
Reputation
Nebula updates the five-area profile only when a recorded event supports the change.
See the last 30 days of recorded activity apart from the standing you have retained across current engagements. Work through the records it lists for review, and take the same evidence with you through Take this record.
After the finish
Take a finished engagement into the next one with its history intact, then use confirmed delivery evidence when you respond.
Your tender trail stays connected after award
Your posting, tender and revisions stay in one trail. An award opens your shared engagement; the resulting agreement still requires acceptance.
Your counterparty-confirmed delivery record can match you to opportunities by service region and engagement value. Self-reported profile fields do not affect that match.
Browse opportunitiesMarketplace choice
See organisations grouped by recorded reputation tier in the signed-in marketplace, and which have no recorded history. Ask for the scores out of 100 and recent reputation events; an owner or administrator at the other organisation decides the release.
Begin with one job and your own team: add the agreement it runs on, review what Nebula reads and keep the first report it prepares. The other party can join when it helps.
Or sign up and start now, or work with Nebula through the founding programme.
