Seat Price or Feature Pack? The Quote Shape Changes the Bill
Prefer a per-seat quote when many people run few methods and you can name who counts as a seat. Prefer a per-feature or feature-pack quote when few people run many methods and you can name which methods sit in the SKU. Per-seat versus per-feature pricing for plasmid design software changes the bill through those two counts, not through a blog that declares one model cheaper. This is not a rematch of what moves plasmid design software cost for a small team. That page owns seats, packs, migration, and lock-in as a set. This page only compares quote shape. Nothing here guarantees that either shape, or any vendor, will cost less.
Match the Quote Shape to Headcount Versus Methods
Write two numbers before you open a pricing page: how many people must design or review maps this year, and how many assembly methods you will actually run. If the first number is large and the second is short — restriction plus Gibson, and that is the quarter — let seat definition and minimum seats control the sheet. If the first number is small and the second is a list — restriction, Gibson, Golden Gate, In-Fusion, plus a reviewer path — let the method pack control the sheet.
Hybrid quotes are common. A vendor can bill named users and still hide a method in a higher tier. Treat that as both axes, not as a reason to pick a winner. Academic versus commercial cloning-software licenses still decide which list you are even allowed to read. Qualification is a contract fact. It is not a third billing model.
What Each Quote Shape Actually Bills
Force both shapes onto the same rows before you look at a dollar.
| Dimension | Per-seat quote | Per-feature or feature-pack quote | Fit implication |
|---|---|---|---|
| Unit on the invoice | Named users or seats | Methods, modules, or a pack of features | The unit you cannot count is the unit that will surprise you |
| Who counts | Designers, and sometimes reviewers and viewers | Whoever needs the packed method, regardless of headcount | A reviewer who must buy a design seat multiplies a per-seat bill |
| Where methods sit | Usually inside the paid seat; a free viewer may not simulate | Inside the quoted SKU — or outside it, as an add-on | A cheap pack that omits Golden Gate is not a saving if that is the method |
| Minimum purchase | Minimum seats, or a custom organization tier | A pack floor, or "all features" versus "one feature" | A three-seat minimum can dominate a four-person lab |
| Qualification | Academic and corporate tables are different objects | Academic packs can omit industry modules | Do not average the two tables into a typical price |
| Honest limit | Headcount growth is linear until viewers are defined | Method growth is linear until the pack is itemized | Neither column is guaranteed cheaper over a year |
SnapGene's pricing page, observed 2026-09-02, is a per-user example: academic subscriptions at 1 / 2 / 5 / 10 users for $350 / $700 / $1,750 / $3,250 per year; corporate at $1,845 / $3,690 / $9,225 / $18,450 per year; student $149 per year; named-user language on the subscription. Viewer mode can view, annotate, and share; it does not simulate cloning. That is methods sitting on the paid seat, not on the free share path. Organization SSO and provisioning are custom on the same page. Treat custom as unpublished until you have a quote.
On the same date, Zettalab's pricing page showed a 60-day trial and monthly cards: Standard displayed $16.99 struck through and $9.9; Team started from $31.25 per seat per month with a three-seat minimum; Custom said contact sales. Yearly cards were also on the page. The same page's FAQ, under "What is the cost of this platform?", said all features are available for 10/month and individual features at $5/month each. Those FAQ figures do not match the cards. Record both. Do not synthesize one official Zetta price, and do not treat either number as proof that a per-seat card is cheaper than a feature pack, or the reverse.
The Trade-Off a Price Card Cannot Show
A cheap seat that cannot simulate the method you run is not cheap. You will buy the pack later, or you will keep a second tool. A cheap pack that forces every reviewer onto a design seat is not cheap either. You will pay for people who only needed to leave a comment.
The operational tell is the handoff. If the reviewer can finish in Viewer or read-only, the per-seat row shrinks. If the reviewer must open a simulation window to trust the junction, the per-seat row grows, and a feature-pack story that still bills every opener as a full seat is a hybrid with the worst of both. Write that sentence on the quote before you compare totals. The TCO page still owns migration and lock-in. This page only refuses to let a sticker hide the missing method or the extra seat.
How to Read Published Examples Without Inventing a Winner
Treat a public page as an observation with a date. If two blocks on the same page disagree, record the conflict. Do not tidy the memo by picking the number you like.
SnapGene's tables are a list because SnapGene published them, on 2026-09-02, as per-user annual subscriptions with an academic-qualification rule: degree-granting institution or nonprofit registered charity, academic-research-only use. A small company does not inherit the academic table by calling itself a lab. Zettalab's cards are a per-seat starting point with a feature-pack narrative in the FAQ; the conflict is part of the observation. Benchling's industry cell stays unpublished on this page because this article is not a Benchling quote and no official industry list is being used. A comparison blog that prints a dollar for an unpublished plan is not a source you can show finance.
The live pricing page as published at the time you buy is the source that wins later. Do not treat this article as a reconstructed official price for any vendor.
A Fit-Based Next Step, Not a Cheaper Model
Write headcount and methods on one card. Ask every vendor to price that card: who counts as a seat, which methods sit in the quoted pack, what happens to a reviewer, and what export you keep if you leave. Compare two complete answers, not two stickers. If you still need migration, training, and lock-in lines, go back to the small-team cost page. If you still need academic-versus-corporate qualification, go to the license page.
A lower published number can still lose on seat definition, minimum seats, or a missing method. This page does not guarantee that per-seat pricing, per-feature pricing, or any named vendor will cost less over a year.
Frequently Asked Questions
When should a lab prefer per-seat plasmid software pricing?
When many people run a short method list and you can name who is a seat. Minimum seats and viewer rules still have to be written down. This is not a finding that per-seat quotes cost less.
When should a lab prefer per-feature or feature-pack pricing?
When a small group runs many methods and you can see which methods sit in the quoted SKU. A pack that omits your method is not a saving. This is not a finding that packs cost less.
Is SnapGene a per-seat example?
Yes. The public academic and corporate tables observed on 2026-09-02 are per-user annual subscriptions, with named-user language. Viewer mode is not the full method set. Organization pricing for SSO is custom.
Does a published seat price mean that vendor is cheaper?
No. A public card is a starting observation. If the same page also publishes a conflicting feature-pack line, record both — as Zettalab's 2026-09-02 cards and FAQ did. This page does not guarantee either shape or vendor costs less.
Related Articles