pitch.gigs.engineering

gigs.engineering

Your PE seal earns on your terms.

↓ scroll · arrow keys

The credential that signs the built world, sitting idle

A PE license is years of exams, supervised practice, and references condensed into one instrument: the seal that makes drawings, calculations, and plans lawful to build from. And for most of the people who hold one, it earns in exactly one way — when an employer bills it — or not at all.

  • The design-firm engineer — seals all day for the firm's clients; the license earns only what the firm's rate sheet says, and the firm's E&O stays at the office when they leave.
  • The exempt-industry engineer — earned the PE anyway, then took a job the industrial exemption covers; the hardest credential of their career is a plaque on the wall.
  • The solo consultant between projects — the license earns until the pipeline gaps, and every working hour is wrapped in business development for the next one.
  • The retired or between-roles license holder — pays renewal fees and PDH hours, year after year, on a live seal that currently earns nothing.

The villain is not the firm, and it is not AI. It is the overhead stack: selling even one evening of licensed review compliantly means your own professional-liability coverage, your own client, your own engagement terms — and in most states your own registered firm, because entities that offer engineering services need their own license too. The apparatus costs more than the work, so the spare judgment goes unsold, and the improvised alternative is a board complaint waiting for its moment.

One candour before anything else, because for the design-firm engineer it comes before all of that: your employment agreement. Whether outside sealing is permitted at all — and what counts as a conflict if a Set ever touches your firm's clients — is a question between you and your contract, and it is the one gate this platform cannot clear for you. The exempt-industry, solo, and retired postures carry no such gate. What the structure does give every posture is the same honest instrument: discipline, state, and scope are visible before you claim, so nothing here ever asks you to open a Set blind — and a skip costs nothing and is invisible to your record. If your agreement says no, this door is not for you yet, and we would rather say so here than meet your firm's counsel later.

Postedncees.org/licensure/

The reserved act is real, not rhetorical: engineering licensure runs state by state through NCEES-member licensing boards, and only a licensed PE may seal engineering work where the law requires a seal. That statute line is why this door exists — and why it recruits license holders only.

Three steps, none of them hard

  1. Verify. Your PE — or SE, where a state reserves structural work to it — checked against the state board's official roster: license, discipline, states, standing. No essays, no interviews, no profile to groom.
  2. Claim. A matched Set reaches your phone: discipline, state, scope, and the flat Review Fee, already fixed. Claim it and the full Set unlocks — drawings, calculations, plans, and the questions the preparation flagged for licensed judgment. Skip it, and that costs nothing and is invisible to your record.
  3. Seal — or don't. Review the Set into your responsible charge. Seal it, send it back with defects noted, or decline with a memo. Every one of those outcomes is completed professional work, and every one pays the same flat fee.

Routing is designed as a lattice, not a pool: license × state × discipline × standing × coverage × review-and-seal legality — that last axis a per-state map still pending, stated on the authority slide — evaluated fresh per Set. A California structural license never surfaces a Texas geotechnical Set. No score overrides a license, and no algorithm's mood widens your scope — your declared competence narrows it further, because that is your professional obligation and the router's job is to respect it.

fee levels and review turnaroundPendinggate: first live fee data

▮▮▮posts when first live fee data resolves · ▮▮▮posts when first ninety days of measured completions resolves — the live door states its payout and minutes as design targets, and this record keeps them exactly that: targets, never measured facts, and no figure appears here before it is measured.

How the money works — and why it is never a "seal fee"

  • Fee-certainty: the Review Fee is flat and fixed at post time — never a share of construction value, never a tier computed after the fact, never adjusted retroactively.
  • Fee-visibility: the number on the card is the number you're paid, disclosed before you claim.
  • Decision-independence: seal, send back with defects noted, or decline with a memo — the fee is identical. Your judgment is never priced, and nobody upstream can make an approval worth more than a refusal.
  • Refusal is sovereign: a send-back is paid professional work; a declination is paid, requires only your reasoned memo, and is final against every process, meter, and operator. Structurally — the system cannot commit past your refusal.

The name is deliberate. A fee named for the seal would price the outcome, and pricing the outcome is the plan-stamping incentive: the pressure to stamp what you haven't reviewed. Here the unit of payment is the review — the licensed judgment — so the economics never lean on the seal. There is no revenue anywhere in this structure that arrives only if you approve.

Responsible charge is the product, not the fine print

Demand enters the cell → the cell's own licensed engineering entity engages you → you review the Set into your responsible charge → seal, send back, or decline — under your own license, in your own judgment, with coverage naming you.

What a buyer purchases through this cell is not drafting labor — it is a decision with liability behind it: a licensed engineer's seal, applied only to work reviewed into their responsible charge. That rule is not ours: responsible charge is the licensure statutes' own term of art, defined state by state — and the structure is built so honoring it is always the economically rational move.

Postedwww.nspe.org/sites/default/files/resources/pdfs/Ethics/CodeofEthics/NSPECodeofEthicsforEngineers.pdf

The profession's own code is the design spec — NSPE Code of Ethics, Rules of Practice II.2: engineers shall perform services only in the areas of their competence, and shall not affix their signatures to any plan or document dealing with subject matter in which they lack competence, nor to any plan or document not prepared under their direction and control. That signature rule is the plan-stamping line — and exactly why the fee here never rewards the stamp.

Read that quoted clause against this product and you find the hardest question on this slide, so we put it on the slide: a routed Set is prepared by AI — not under the reviewing engineer's direction and control from the first line. Whether reviewing another party's work into responsible charge — adopting it as your own through genuine licensed review — is lawful sealing, or whether a state's review-and-seal and successive-seal rules treat it as the plan-stamping the code forbids, is a question state boards answer differently, state by state. This structure does not argue with any board's answer; it routes around every state whose answer is no.

Pendinggate: per-state review-and-seal / successive-seal rules mapped; lattice routes Sets only where review into responsible charge is lawful

The per-state map of review-and-seal legality — which boards permit an engineer to seal work not prepared under their direction and control when it is reviewed into their responsible charge, and on what conditions — is in progress, not done. No state's answer is assumed: this axis joins the routing lattice before the first Set routes, and a state whose rules make review-and-seal unlawful never surfaces a Set to its engineers.

Pendinggate: master professional-liability (E&O) program quoted, naming rostered engineers

The live door says "we plan to carry the professional liability coverage," and this record keeps the tense honest: the master E&O program naming rostered PEs is designed, not bound. Underwriter appetite for AI-prepared engineering sets is the real question, and nothing is sealable before coverage naming the engineer is in force. Stated pending, because the coverage promise is the load-bearing one.

The economics, candidly

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

Functions migrate Human → Agentic → Generative → Code until they hit their vertical's floor, and engineering's floor is written in statute: modeling, calculations, drafting, and code-checking all migrate, and the sealed act does not — a licensed human in responsible charge is the law's own termination condition. That is why this membership exists and why it appreciates as the software improves: better preparation makes your review minutes more productive; it cannot replace the license.

One cell, one door open — the rail is named after the demand is real

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

Every gigs.* expert door runs one motion — B2H2A, business to licensed human to agent — and only that motion, because a statute names a person. The sibling cells opened both doors at once: gigs.lawyer with api.lawyer, gigs.claims with api.insure. This cell is candid about being earlier: the demand rail for sealed engineering work is not yet a named brand. Demand is designed to arrive from workflows across the estate that terminate in a document only a PE can lawfully seal, and the rail brand is queued behind this door — supply is the binding constraint, so the supply door opens first.

Postedgigs.engineering

gigs.engineering serves: the live door runs the early-access funnel — license type, discipline, states — and says plainly that it is early access, not a live marketplace. The namespace position is occupied.

Where it stands, stated plainly

Pendinggate: entity formation and firm licensure (Certificate of Authorization or state equivalent) in the first state

The operating entity is designed, not formed — and in engineering, formation is not enough: an entity offering engineering services needs its own firm license, state by state. The first state is not yet named; the founding cohort's licenses are an input to naming it. No Set routes before the entity, its firm licensure, and its coverage exist.

Pendinggate: first routed Set sealed and settled cold end-to-end

The full path — demand in, routed Set, licensed review, seal or refusal, coverage in force, flat fee paid — flips to posted on its first cold settlement, with the evidence URL, not before. Until then, early access means exactly that: verification is real before the word "verified" is.

If nothing changes: the seal keeps earning for everyone but you — or the improvised alternative, which is the board-complaint trap this platform exists to replace.

If it works: a well-scoped review on a weeknight, inside your discipline and your states, paid the flat fee the card showed before you opened the Set — a license turned from a cost you carry into an asset that earns.

Apply for early access at gigs.engineering — founding engineers verified before routing begins hold first-Set priority in their licensed states and disciplines, and the founding cohort's bar of licenses shapes which state's firm licensure goes first. Every founding applicant gets the fee memo before routing begins — how the money works, why the fee is flat and never a seal fee, who insures what — one page, written to be forwarded before you touch an outside Set.