Engagements
Bring KBPD to a team you trust .
Per-named-seat licensing for client teams. Delivery records, no DRM. The pattern we use when a company puts a few of its engineers on the same KBPD stack and wants the license to scale with the team — not with self-serve checkouts.
The model
Three coupled decisions.
Each is named explicitly because it's where similar products are usually vague. Buyers who need anything different self-select out before the sales call.
-
Unit of license
The individual engineer.
Seats are named by email. 5 engineers = 5 seats, priced linearly. Aligns revenue with team size, survives engineer turnover, gives a per-person grant instead of an unlimited company license.
-
Delivery
A secure download link per engineer.
Each licensed engineer receives their own download URL via email. Same artifact, per-seat delivery channel. Per-engineer audit trail without scanning anyone's machine. Installation is a single
tar xzf. -
Enforcement
Contract and delivery records. No DRM.
No license key. No runtime check. No kill switch. The grant is legal, not technical. The contract names the seats, the delivery record shows what was delivered, and a quarterly seat-list confirmation closes the audit loop.
Onboarding
Five steps. No surprises.
- 01
Master agreement.
We sign a service agreement that names the term, the seat count, the per-seat rate, and the audit terms. One document covers the engagement.
- 02
You provide the seat roster.
A list of engineer emails. Each will receive their own delivery channel and appear in our per-licensee delivery records.
- 03
We deliver per-engineer download links.
Each engineer gets a one-time URL to download their copy. The artifact is the same across the team; the channel is per-seat for the audit trail.
- 04
Each engineer installs locally.
One tar extraction into their workspace. The IP-boundary check prevents accidental leakage to client-owned remotes (this is structural, not a paywall).
- 05
Refresh on every release.
New version ships from the source system → we rebuild your archive → email active seats with refreshed download links. Quarterly we ask you to reconfirm the roster.
If it matters to you
Things this model does not do.
- No kill switch. If a seat lapses, the engineer keeps the copy they already downloaded. We stop sending updates; we don't reach back and delete.
- No remote shutoff. The license is the contract. If a contract is breached, that's a legal conversation, not a firmware update we push.
- No per-skill granularity. One license grants the whole methodology. We may add tiered entitlements later when volume justifies the infrastructure; we don't have them now.
- No silent enforcement. The audit cadence is agreed in advance, quarterly. You always know what we're checking.
If you need any of the above, you probably need a different product — a SaaS-style license server with per-seat key enforcement and remote disable. We build that conversation honestly: this isn't it. The teams we work with want methodology, not a paywall, and a master agreement is the right enforcement layer for that.
Pricing
Every engagement is bespoke.
Each team is a different size, working on a different stack, with different renewal cadences. Per-seat rates depend on team size, term, and whether you're a founding engagement (closing the launch window) or standard.
Tell us what you're building and how many engineers will be on it. We'll come back with a proposal — usually within two business days — that names the seats, the rate, the term, and the audit terms in plain language.
For solo developers and small teams who want the methodology without the contract overhead, the self-serve Starter Kit covers the same artifact set for a one-time fee.
Open a thread
Tell us who's on the team.
Seat count, term you're thinking, the codebase the team will be on. We'll scope it and reply with a written proposal — not a templated SaaS form-letter.