Skip to content
StartStart a project

Team OS for small software & AI teams

Build it.Prove it.Split it.

SandPalace runs small teams that ship client work with humans and AI agents. Your GitHub history is the evidence. Every dollar a client pays is split across everyone who created value. And 20% waits out the warranty.

Start a projectSign in

Humans + agents · few people · many clients · zero ceremony

project.samplein progress

[00] Sound familiar?

Small teams do big work. Then the money gets weird.

  1. Who brought the client?

    01

    The intro, the pitch, the dinner that closed it. Usually forgotten by the third invoice.

    Origination gets its cut

  2. Who actually built it?

    02

    Timesheets nobody believes. Half the code was written with an agent anyway.

    GitHub is the record

[01] Evidence

Work is the evidence.

Connect GitHub and get back to building. Commits, pull requests and reviews become the record of who built what, including the commits an AI agent helped write.

  • No timesheets. No “what did you do this week” forms either.

  • Reviews count. Reviewers get a share of Delivery. Catching bugs is building.

  • Agent commits count. The agent did the typing. You did the work.

evidence.log — forecast-appsample data
  1. Commitdocs: training guide for demand plannerse90d4a1@dev✦ agent-assisted
  2. Commitfix(etl): handle missing route data7c2e10b@dev✦ agent-assisted
  3. ReviewApproved PR #128 · 3 comments#128@reviewer
  4. PRPR #128 · Export forecasts to Excel#128@dev
  5. Commitfeat(forecast): weekly demand model per SKUa1f3c9e@dev✦ agent-assisted
Commits
38
PRs
9
Reviews
14
Timesheets
0

[02] The split

Everyone who made it gets paid.

Each project's revenue splits across the whole value chain. Not just whoever typed the code.

Sample project · forecasting desktop app

$71,000

10%
15%
60%
15%

  • Origination

    10%

    $0

    Whoever brought the client in.

  • Account

    15%

    $0

    The face of the project: contract, follow-up, collections.

  • Delivery

    60%

    $0

    Build, ship, document, train. Reviewers get a share.

  • Organization

    15%

    $0

    Tools, AI spend, overhead. The lights stay on.

Template: default · editable

Splits are templates. Change them per project, decided by the project owner or by the team.

[03] Warranty

Quality has skin in the game.

20% of every payout is held back during the warranty, 30 days by default. Ship something solid and it comes back to you in full.

  1. Bugs go home first. A bug is routed back to its author before anyone else touches it.

  2. Fixers get paid. Whoever fixes it is paid from the held-back share.

  3. Day 31 is different. After the warranty, fixes are billed to the client or covered by the organization.

Delivery payout · @dev · sample

$42,600

Day 00 / 30

Paid at delivery · 80%$34,080
Held 20%
Day 0Day 30
  1. D00Delivered. $34,080 paid now, $8,520 held.
  2. D09Bug #41 reported → routed back to its author first.
  3. D12Fixed by @reviewer → $1,200 paid from the held share.
  4. D30Warranty closed → $7,320 released to @dev.

Day 31+: billed to the client or covered by the org.

[04] Origin story

Built around a real job.

SandPalace started with a demand-forecasting desktop app for a large dairy company. One developer shipped it, mostly with AI agents. A partner brought the client, ran the contract and handled the payments.

Old tools had no idea how to pay that team fairly. So we built one that does.

  1. The partner

    Brought the client. Signed the contract. Followed up and chased the payments.

    • Origination 10%
    • Account 15%

  2. The developer + agents

    Built, shipped, documented and trained the users. Mostly by directing Claude Code.

    • Delivery 60%

  3. The organization

    Paid for the tools and the AI spend. Kept the lights on.

    • Organization 15%

[05] How it runs

From kickoff to payout. No forms in between.

  1. Open a project

    Pick a split template. Keep the default or change it.

  2. Connect the repo

    Link GitHub. That is the whole setup for evidence.

  3. Ship

    Commits, PRs and reviews log themselves. Agents included.

  4. Get paid

    Client pays, everyone gets their cut. 20% waits out the warranty.

[06] Made for 2026

Built for how teams actually work.

  • Humans + agents

    Agents write a lot of the code now. Humans direct it, review it and own it. The record keeps both.

  • Few people, many clients

    Three people, five client projects. Each one carries its own split.

  • Zero ceremony

    No timesheets. No status reports. No standups for the sake of standups. Ship, and the record writes itself.

  • The team decides

    The project owner or the whole team sets the split. The software just keeps everyone honest.

[07] FAQ

Fair questions.

Do AI-assisted commits count?

Yes. Commits written with an agent are part of the evidence like any other. AI spend comes out of the Organization share, not out of anyone’s pocket.

Do we have to use 10 / 15 / 60 / 15?

No. That is the default template. Splits are templates you can change per project, decided by the project owner or by the team.

Do reviewers get paid?

Yes. Reviewers get a share of Delivery. Reviewing is part of shipping.

What happens when a bug shows up?

During the warranty (30 days by default), it goes back to its author first. Whoever fixes it is paid from the 20% that was held back.

And after the warranty?

Fixes are billed to the client or covered by the organization. Nobody works for free on day 31.

Do we need to track hours?

No. GitHub is the record: commits, pull requests and reviews. Nobody fills in a timesheet.

Who is it for?

Small software and AI agencies, freelancers forming a team, and the clients who hire them.

Your move

Start the next project fair.

Set the split, connect the repo, ship. Everyone who creates value gets paid for it.

Start a projectSign in