pitch.gigs.accountants

gigs.accountants

Get paid to approve the close.

↓ scroll · arrow keys

Judgment that only earns when someone else's calendar says so

The villain is not the employer, not the client, and not AI. It is the engagement apparatus: there is no compliant unit of sale for an hour of controller judgment. Any side engagement demands scoping, an engagement letter, your own E&O, invoicing, collections — a fixed cost that makes small, honest units of review work uneconomical, and makes improvised moonlighting a coverage-and-independence trap.

One membership, sized to a close package

The offer is one shape, repeated: a close-review Gig. The Brief comes first — entity profile, period, what the package contains, which questions the preparation flagged — and the flat Close Fee, fixed at post time and disclosed before you claim. Claim it and the full prepared package unlocks: reconciliations, accruals, flux analysis, journal entries, tie-outs, each with the preparation's own flagged uncertainties in front of your judgment.

Three outcomes, all of them completed professional work, all paid the same flat fee:

Work is matched inside your credential, your jurisdictions, and your declared competence — a package never surfaces that your certificate can't stand behind. The independence trap named above is treated as a matching problem too: the design has members declare employer, firm, and restricted entities at verification, and excludes any package from an entity on that list — your own employer, your firm's attest clients — before it can reach your queue. Your Register — the running record of what you approved, sent back, and declined — accrues to you, not to the platform.

Pendinggate: conflict and independence screening implemented in the matching pipeline

Conflict and independence screening is designed, not yet running: employer, firm, and restricted-entity declarations at verification, matched against every package's entity before it surfaces. Nothing about this door's matching goes live ahead of that screen, and this claim flips to posted when the screen is demonstrably in the pipeline.

The hard line: nothing on this door is attest. Audit opinions, review engagements, attestations, and tax sign-off are reserved acts and belong to gigs.tax, the family's door for CPAs and EAs working under that machinery. The moment a package would cross that line, it is not a Gig here.

Postednasba.org/stateboards/

The attest boundary is real, state-board machinery, not this door's invention: audit and attest practice is regulated per state by boards of accountancy, which is exactly why this door scopes to close review and routes reserved acts to the family door built for them.

Pendinggate: E&O program bound naming rostered members

The design requires E&O naming the member before anything is approvable. The program is designed, not bound; nothing goes approvable before coverage is in force, and this claim flips to posted with the binder in evidence.

Three steps, none of them hard

  1. Verify. Your CPA or CMA credential, checked against the issuing body's official record. No essays, no interviews, no profile to groom.
  2. Claim. A matched close package reaches your phone: entity profile, period, package contents, flagged questions — and the flat Close Fee, already fixed. Claim it and the package unlocks. Skip it, and that costs nothing and is invisible to your Register.
  3. Approve — or don't. The package is sized to be read in one sitting — a design target, not a measured fact. Approve it, send it back with defects noted, or decline with a memo. Every outcome pays the same flat fee.

How the money works

close-fee band and turnaroundPendinggate: first live fee data

▮▮▮posts when first live fee data resolves · ▮▮▮posts when first ninety days of measured completions resolves — what a package pays is your first question and it deserves a number, not adjectives. The band posts here the moment real packages price it, and until then the structure above is a design fact stated in the indicative — no figure is asserted in advance.

The honest floor — there is no statute here

Human~95% of function cost
Agenticorchestration-priced
Generativeinference-priced
Codenear-zero marginal

In the family's licensed cells, the migration of work from humans to software stops at a statute: a reserved act names a person, and the law holds the floor. This door claims no such floor, and says so in its own deck. Nothing in the accounting close is statutorily reserved; the preparation has already migrated and will keep migrating.

What holds instead is an accountability floor. What the rail's buyers need is not labor — the preparation is the machine's — it is an approval a named professional stakes standing on, because the people downstream of the numbers (auditors, lenders, boards) rely on exactly that. A softer floor than a statute, priced honestly: the flat fee prices judgment and staked standing, never hours — and this record does not pretend the floor is harder than it is.

Both sides of one rail

B2Abusiness serves an agent — the machine is the customer
B2Dthe developer reads the catalog like API docs — key funnel on the rail
A2Aagent to agent — pure machine commerce
B2A2Ba business system calls the rail on its own behalf
B2A2Dour agent serves the deputized developer
B2A2Cour agent serves the consumer
B2H2Aa statute names a human — the licensed supplier in the pathprimary
A2H2Athe human is a required supplier: the regulated-cell shape

gigs.accountants and apis.accountants are designed as two faces of one pair: the demand rail is where agents and business systems will buy close review; this door is where the credentialed humans who supply it are recruited. Business to human to agent — B2H2A — the only motion any gigs.* door runs. Here the person is named by reliance rather than statute, and the pathNote in this record's own frontmatter carries that distinction.

Postedgigs.accountants

This namespace position is occupied and candid: gigs.accountants serves a reserved page naming itself the accounting supply face of the gigs estate. Reserved means reserved — the page implies no live marketplace.

Postedapis.accountants

The other face is held with the same candour: apis.accountants serves a reserved page — "Reserved for the accountants' door of the apis family" — a held namespace position, not a live rail.

Postedgigs.lawyer

The family pattern this door inherits is live, not hypothetical: gigs.lawyer serves today as a recruiting door with candid early-access framing.

Postedgigs.tax

gigs.tax — the family's reserved-act door and this door's hard exclusion boundary — serves today on the same early-access footing.

Postedgigs.expert

gigs.expert, the family's open generic door and the Ask below, serves today with a live application flow.

Where it stands, stated plainly

Pendinggate: brand config lands in the gigs family worker registry

This door does not recruit yet. The family worker adds a door as one config file plus one registry line — a design fact of the substrate — and gigs.accountants ships its recruiting surface behind exactly that gate, replacing today's reserved page.

Pendinggate: per-state counsel analysis of title use and firm-registration triggers

Members hold CPA and CMA credentials, and some states regulate how the CPA title is used even outside attest work. Whether close review under a member's title triggers any state's firm-registration or holding-out rules is counsel-gated, per state; the door opens state by state behind that analysis, not ahead of it.

Pendinggate: apis.accountants record drafted and rail surface live

The demand rail's own G4 record and surface are not yet drafted; today it is a deliberately held, honestly reserved namespace position. This door's liquidity claim posts only when the rail routes a real package — supply doors that imply demand before it exists are exactly what this family refuses to be.

supply pool depth and routed-package volumePendinggate: StartupsStudio/stack#1

▮▮▮posts when stack#1 §A5 resolves · ▮▮▮posts when stack#1 §A5 resolves — no pool or volume figure is asserted anywhere in this deck; both are measured after the door opens, never estimated before it.

The open door today is gigs.expert — the family's generic door for credentialed professionals.

Pendinggate: accounting cohort listed on gigs.expert's posted professions

gigs.expert serves a live application flow today and its credential step takes whatever credential you hold — but its posted professions read legal, engineering, tax, medical, claims, and do not yet name accounting. This door opens on the accounting cohort, and founding applicants carry over with their place held in order of application, only once that cohort is listed; until then the honest instruction is the one this deck gives: apply, and state the CPA or CMA at the credential step.

If this was forwarded to you: gigs.accountants is the reserved supply door where credentialed accountants will get paid flat, disclosed-up-front fees to review and approve AI-prepared close packages on their own schedule — approve, send back, or decline, all paid the same. It is candidly pre-launch: the domain serves a reserved page, the recruiting door is gated, and every claim above carries its own state and evidence. If you close books for a living: apply at gigs.expert and state your CPA or CMA when the credential step asks. If you know who does: forward this.