Approval-only private pilot

Build together.
Stay aligned.

One shared operating space for partners managing ownership, commercial work, delivery, and decisions.

Approval-only pilotPrivate by designBuilt for partners

Projects & Revenue in a pilot workspace. Fictional data.

Six records the partnership actually runs on

Each one has its own place, its own approvals, and its own history. Nothing is inferred from anything else.

Ownership

Partners, roles, and recorded ownership positions, changed only through an approved decision.

Projects & Revenue

Commercial work: contracts, recorded revenue, and the share basis agreed for each project.

Tasks

Delivery work with owners and due dates, a separate lane, never mixed into revenue.

Contributions

Cash, assets, and time put in by each partner, logged as its own record type.

Decisions

Proposals, who approved them, and the tasks or records they changed. Traceable both ways.

Settlement readiness

A checklist view of what is agreed, outstanding, or unresolved before partners settle up.

Shared business visibility

Every partner reads the same page

Ownership positions, commercial performance, open delivery work and pending approvals sit in one workspace. Role-based access decides who can propose, who can approve, and who can only read.

  • One workspace per partnership, approval-only.
  • Every record shows who entered it and who approved it.
  • Figures are stated, not derived. No automatic calculation.
Workspace overviewNorthwind Studio · Q3

Recorded ownership

Partner A40%

Partner B30%

Partner C20%

Open decisions

1Awaiting approval

3Linked tasks

£56,000Recorded revenue

Projects & RevenueCommercial record, separate from delivery tasks
ProjectsRevenueShare basis
ProjectClientStatusContract value
Harbour identity refreshKestrel FoodsIn delivery£148,000
Atlas platform retainerAtlas GroupActive£96,000
Meridian launch campaignMeridian RailScoping£54,000

Projects & Revenue

Commercial work has its own lane

A project holds the contract, the revenue entries partners recorded, and the share basis they agreed. Delivery work lives in Tasks and links back, so progress never quietly becomes a financial claim.

Projects & Revenue
Contracts, revenue entries, share basis
Tasks
Delivery work, owners, due dates
Never combined
Linked by reference, kept as separate records

Decisions to tasks

A decision leaves a trail

Proposals are raised, approved by the partners whose roles require it, and turned into delivery tasks. The record keeps the reason, the approvals, and everything the decision changed.

  1. 01

    Proposal

    A partner proposes a change, share basis, a new project, a reimbursement.

  2. 02

    Approval

    Required approvers are named by role. Votes and comments stay attached.

  3. 03

    Record updated

    The affected record changes with a reference back to the decision.

  4. 04

    Tasks created

    Follow-up work appears in Tasks with an owner, due date, and its origin.

Decision · Northwind Studio

Change share basis on Atlas retainer

Reason recorded: Partner C is taking delivery lead from October, and the partners agreed to revisit the basis for the retainer only.

Approved · Partner AApproved · Partner BAwaiting · Partner D

Tasks it would create

Update retainer share basis record Partner A

Note change in partner handbook Partner B

Confirm with external adviser Partner C

Approval inside PactBase records agreement between partners. It does not create a legal instrument.

Kept distinct

Seven things partners usually blur together

Most partnership friction starts when one of these is mistaken for another. In PactBase each is its own record with its own approval path.

OwnershipRecorded position in the partnership.

Revenue shareThe basis agreed for splitting recorded revenue.

EquityInstruments held outside the working split, noted as reference.

ContributionsCash, assets, or time a partner put in.

ReimbursementsExpenses a partner expects back, once approved.

Partner loansMoney lent to the business on recorded terms.

SettlementsWhat remains open before partners settle between themselves.

Not in scopeAccounting, payroll, tax, banking, legal records.

Privacy & security

Private by design, approval by default

Workspaces are closed. Restricted administration access is scoped to the active super administrator. Sensitive changes need the approval rules recorded for the workspace.

Read the security overview

Restricted administration

Administrative sign-in is limited to the active super administrator.

Workspace isolation

One partnership per workspace. No cross-workspace visibility.

Traceable history

Every record keeps its author, approvals, and change history.

Encryption

Encrypted in transit and at rest. Super-admin MFA is enforced for privileged access.

Pilot pricing

Pricing is being finalised

During the private pilot, workspaces are provisioned by approval. Pilot partners are told the commercial terms before anything becomes chargeable.

Access

By approval

Pilot term

Agreed per workspace

Price

Being finalised

Request access

Ask for a pilot workspace

Tell us about the partnership. Sending the request opens your email application, and the PactBase team can reply directly.

  • No card, no checkout, no automatic provisioning.
  • No public account is created by this form.
  • Your email application controls delivery of the enquiry.
Which records matter most today?

Sending this opens your email application. PactBase does not store website enquiries through this form.

FAQ

Before you ask for access

Still unsure? Write to hello@getpactbase.com.

Is PactBase accounting software?

No. PactBase records what partners agree and approve. It does not produce accounts, calculate tax, run payroll, move money, or hold legal records.

Are the financial figures calculated for us?

No. PactBase keeps records entered and approved by partners. It does not calculate entitlements, tax, payroll, or settlement amounts.

Who can see our workspace?

Access is limited to the people and roles recorded for that workspace. Public website access never exposes workspace data.

Why is access approval-only?

PactBase is designed for operating relationships that need a deliberate shared record. A submitted website enquiry opens an email only; it does not create an account or workspace.

Does an approval in PactBase bind us legally?

No. PactBase preserves the operational record of an agreement. It is not a legal instrument or a substitute for professional advice.

What happens to our data after the pilot?

Data handling and retention details will be stated in the final reviewed legal notices. The public privacy and terms pages remain available while that review is completed.