Guestlist

June 25, 2026

Public disclaimer: This is an independent public teardown based solely on publicly available information retrieved on 2026-06-25. It is research support, not investment, legal, tax, or financial advice. Company-provided statements are labeled as claims, not verified facts. Guestlist did not participate in or review this report. Errors and omissions are possible; final decisions remain with the reader.

Guestlist is trying to rate the doors on a web that increasingly decides who gets to knock. The company pitches a free Python library and HTTP API that tells AI and computer-use agents which domains are likely to let them in before they waste browser time or unlocker spend (Guestlist homepage; Guestlist docs), and a public PyPI package has been live since late May 2026. That is a sharp wedge inside a real agent-infrastructure buildout. It is also the kind of wedge that only matters if the signal becomes a control point, not a convenience feature folded into someone else's stack. The public record confirms the product surface; it does not yet confirm where the durable value sits. Read the teardown before a clever routing layer gets mistaken for durable infrastructure.

What The Company Does

Guestlist markets itself as a pre-crawl website-access grader for AI and computer-use agents. The company says teams can check a domain before they spend browser time, proxy budget, or retries, and receive a five-tier answer — green, yellow, orange, red, or unknown — plus blocker labels such as Cloudflare, Akamai, DataDome, Imperva, and PerimeterX (Guestlist homepage; Guestlist docs) company claim.

The public surface is self-serve and developer-led. A homepage, signup flow, login flow, documentation hub, and Python package are all visible in public, while the PyPI package shows version 0.2.0, an MIT-licensed client, and a 2026-05-30 release date; the signup page offers immediate API-key onboarding inference / source-backed fact.

What is not public matters as much as what is. The company pages present Guestlist as free, but they do not disclose paid tiers, quota logic, named customers, or a legal entity on the public pages reviewed here (Guestlist homepage; Guestlist docs) inference. That leaves the commercial model, adoption base, and ownership structure at unknown from public sources.

Key Takeaways

Investor reaction
Guestlist is worth one tightly scoped founder call only if the founder can bring proof that the ratings are trusted, used repeatedly, and separately budgeted; otherwise the current evidence still reads as a clever feature rather than a venture-backed company.
Current verdict
hold with medium confidence.
Why investors might lean in
The product attacks a real cost center upstream of browser and unlocker spend, in a market where Browserbase, Bright Data, and Firecrawl already prove teams pay for web-access infrastructure.
Why investors might pull back
Public traction is thin, no customers or pricing are visible, founder background is only partially confirmed, and Cloudflare's signed-agent shift may move the control point away from Guestlist's current probe model.
Highest-leverage fix
Arrive with one proof packet that combines recurring-user evidence, a live-domain accuracy benchmark, signed-versus-unsigned results, and a real pricing or unit-economics story.
Best next move
Take one time-boxed founder call only after that proof packet is shared; otherwise keep the company on watch until the evidence arrives.

What Makes This Potentially Fundable

The fundable version of Guestlist is not a helper script. It is the routing and reliability layer that agent stacks call before they decide whether to browse, unlock, or skip. If that signal becomes trusted enough to sit upstream of meaningful browser and unlocker spend, the product could expand from a simple domain check into workflow routing, benchmark data, vendor selection, and standards intelligence across agent infrastructure.

The timing case is real. Gartner says 40% of enterprise applications will include task-specific agents by end-2026, and Anthropic's computer-use documentation shows the behavior Guestlist is targeting is already productized at a major model platform. Adjacent vendors such as Browserbase, Bright Data, and Firecrawl already monetize the spend Guestlist is trying to protect. That proves the budget corridor exists.

The honest gap is that none of the load-bearing steps are independently proven yet. The public record does not show repeat usage, false-green or false-red rates, signed-agent compatibility, or a paid SKU. Until those appear, the upside is a category option, not an underwritten company outcome.

The Four Holes To Close Before Fundraising

Hole	Investor Fear	What To Bring
There is no independent benchmark for predictive accuracy.	Investors will fear the score is interesting in theory but too noisy or stale to trust in production routing.	Bring a live-domain benchmark with false-green rates, false-red rates, `unknown` share, refresh cadence, and signed-versus-unsigned comparisons where relevant.
There is no proof of recurring users or design partners.	Investors will fear the product is still founder self-use or launch curiosity rather than a workflow dependency.	Bring three recurring-user stories or referenceable design partners, plus usage depth and retention by cohort.
There is no public pricing or unit-economics story.	Investors will fear Guestlist creates value that larger browser or unlocker vendors will capture instead.	Bring current pricing tests, quota logic, budget-owner evidence, and a simple cost-to-serve model tied to real probe behavior.
Founder background, entity, and team coverage are still thin.	Investors will fear the hardest build is undercovered and the company is not diligence-ready.	Bring a canonical founder profile set, relevant prior work, full-time status, incorporation details, and the plan for reliability, legal, and go-to-market coverage.

Decision Snapshot

One-sentence company description: Guestlist is a very early pre-crawl website-access grading layer that tells AI and computer-use agents whether a target domain is likely to let them in before they spend browser time or unlocker budget.
Screen: hold.
Confidence: medium.
Suggested next action: Take one tightly scoped founder call only after a proof packet is shared on accuracy, recurring usage, signed-agent relevance, pricing, and founder background.
Why this matters now: The agent-access category is forming quickly, but the control point may settle inside larger browser, unlocker, or authenticated-agent platforms before a standalone grader proves it owns budget.
Investor-readiness diagnosis: Guestlist has a sharp wedge and real product surface, but not enough outside-the-room proof yet to justify deeper diligence momentum.
Best founder use of this report: Treat it as a proof checklist for turning a technically interesting layer into a company that customers trust, depend on, and may pay for separately.

IC Disagreement Map

The evidence was reviewed independently across five partner lenses working from the same public record: the power-law lens tested fund-returning upside, the prepared-mind lens tested category structure and timing, the founder-jockey lens tested team fit, the risk-reduction lens tested critical flaws, and the long-horizon lens tested value capture and follow-on logic.

Power-law partner
holdmedium confidence
A fund-returning outcome is still conceivable if Guestlist becomes the routing intelligence layer for fragmented access conditions, but today's public record does not prove compounding data, trusted accuracy, or budget ownership.
Would flip on
Repeat production usage, a trusted benchmark, and early monetization would move this partner toward pursue; proof that the feature stays diagnostic or bundleable would move this partner toward pass.
Prepared-mind partner
holdmedium confidence
The wedge is sharp and category timing is real, but the current evidence does not show that a pre-flight grade becomes a durable budget line instead of a freshness-decaying feature inside broader web-access stacks.
Would flip on
Strong predictive accuracy on live workflows, recurring paid usage, and a clear reason buyers want a neutral layer would move this partner toward pursue; evidence that signed-agent traffic or bundling erodes the wedge would move this partner toward pass.
Founder-jockey partner
holdmedium confidence
A real product is in market and the founder appears close to the problem, but the public record still does not independently prove the founder depth, full-time commitment, or team coverage needed for an adversarial infrastructure build.
Would flip on
A canonical founder profile, verified prior technical depth, and real early users would move this partner toward pursue; shallow background, part-time status, or no trusted users would move this partner toward pass.
Risk-reduction partner
holdmedium-high confidence
Guestlist may solve a real pain at the wrong layer: value capture, technical efficacy, and platform-shift risk are all unvalidated, but a fatal flaw is not yet conclusively proven from public sources alone.
Would flip on
An independent benchmark, customer willingness to pay on top of existing access tools, and signed-agent resilience would move this partner toward pursue; weak predictive value or buyer insistence on bundling would move this partner toward pass.
Long-horizon partner
holdmedium confidence
The company fits the fund's theme and stage, but the evidence still does not show a monetizable control point, a reserve-worthy follow-on path, or a dataset that compounds faster than it decays.
Would flip on
Proof of production usage, a paid SKU with margin room, and a benchmarked signal that embeds into customer workflows would move this partner toward pursue; evidence that larger stacks can reproduce or absorb the signal would move this partner toward pass.

After the evidence-request round, all five partners confirmed hold. No vote changed, although the risk-reduction partner raised confidence to medium-high because the public loop closed without new positive proof. The agreement is evidential rather than social: each lens stopped on the same small group of missing proofs for a different reason, while the live disagreement over whether Guestlist becomes a control point or a bundled feature remains intact.

Scenario Range

Scenario	What The Company Looks Like In 3-5 Years	Falsifiable Trigger To Watch	Earliest Evidence
Strikeout	Guestlist remains a clever diagnostic utility, larger browser or unlocker platforms ship a good-enough pre-check, and authenticated-agent lanes make Guestlist's unsigned probe signal too misaligned to command separate spend.	A founder call still cannot show trusted benchmark data, recurring external users, or a buyer willing to pay separately.	A live-domain benchmark fails to show reliable lift, or recurring usage remains shallow and founder-led.
Base	Guestlist becomes a niche reliability add-on for a small set of agent builders, with modest usage and maybe limited paid experimentation, but not a default routing layer with material pricing power.	Users find the signal useful and somewhat trusted, but budgets stay small and the product remains optional inside broader access workflows.	A handful of recurring teams appear, but pricing stays tentative and the workflow dependence is narrow.
Home run	Guestlist becomes the default pre-flight routing and benchmarking layer for agent-access decisions, with a freshness-advantaged dataset that bigger stacks still rely on rather than replace.	Customers route real spend through Guestlist, the benchmarked signal stays predictive even as standards evolve, and a paid SKU earns a durable budget line.	Referenceable production users, strong benchmark results, and clear pricing power appear within the next diligence cycle.

What Investors Will Test

What We Looked For	Current Read	Investor Implication	Founder Prep Priority
Whether the wedge is a real control point.	Guestlist clearly targets the pre-browse decision point on its homepage and in its docs, but no public customer evidence shows that teams route spend through it today.	The first meeting should test workflow dependency, not product description.	Bring recurring-user workflows that show where Guestlist changes routing decisions before browser or unlocker spend.
Whether the signal is trustworthy.	The company documents tier semantics and API fields on Guestlist docs and PyPI, but no public benchmark shows false-green rates, false-red rates, or freshness discipline.	Investors cannot underwrite a reliability layer until the signal is demonstrably predictive.	Bring a benchmark on live domains, including defended domains and signed-agent-sensitive cases where possible.
Whether the market is moving toward or away from this product shape.	The broad agent wave is real according to Gartner and Anthropic, but Cloudflare's signed-agent program may change what "accessible" means in practice.	Timing alone is not enough; the founder must show the product still measures the right battleground.	Bring signed-versus-unsigned comparisons and a roadmap for an authenticated-agent world.
Whether Guestlist can own a budget line.	Adjacent vendors such as Browserbase, Bright Data, and Firecrawl already monetize the surrounding stack, while Guestlist's public surface stays free.	Investors will ask why a buyer pays Guestlist separately instead of demanding the feature inside a broader contract.	Bring pricing tests, quota logic, budget-owner evidence, and a simple unit-economics model.
Whether the founder and team fit the hardest build.	The founder identity chain across PyPI, PyPI user, and Hacker News is directionally consistent, but background depth and team coverage remain thin in public evidence.	Founder-market fit remains promising rather than proven.	Bring canonical profiles, relevant prior work, full-time status, and the plan for reliability, legal, and go-to-market coverage.

Claim Reconciliation: Inconsistencies Investors Will Catch

Only two material inconsistencies surfaced in this research, and both are fixable before a meeting.

Claim Or Metric	Where It Appears	Conflicting / Unreconciled Versions	Why Investors Flag It	How To Reconcile
Product versioning	Guestlist docs PyPI	The docs header still says version 0.1, while PyPI lists version 0.2.0.	Investors read version drift as a small but revealing sign that the public operating surface may not stay synchronized with the shipped product.	Update the docs header, add a simple changelog, and be ready to explain what changed between the two public versions.
Founder identity depth	Guestlist homepage PyPI PyPI user Hacker News profile	The public chain around name, email, and handles is consistent, but there is still no canonical public biography or company about page that resolves background, location, prior work, or legal entity.	Investors will immediately ask who is behind the product, whether the background matches the problem, and who signs customer contracts.	Publish a canonical founder profile, add a short company/about page, and disclose the operating entity before fundraising.

Diligence Findings: Issues To Fix Before You Raise

5 high2 medium

Guestlist has not published an independent benchmark showing that its scores predict real outcomes well enough to route production workflows.
high
Technical diligence
Fix
Run and package a live-domain benchmark with false-green rates, false-red rates, freshness, coverage, and signed-versus-unsigned comparisons.
No public customer proof separates repeat workflow dependency from founder self-use or launch curiosity.
high
Commercial diligence
Fix
Bring three recurring-user or design-partner stories, ideally including one referenceable team and one de-identified workflow map.
The company has not shown how a free-facing product becomes a separate budget line instead of a bundled feature inside a broader stack.
high
Commercial and financial diligence
Fix
Publish or privately share pricing tests, quota logic, willingness-to-pay evidence, and a unit-economics model tied to real probe behavior.
Authenticated-agent standards may change the battleground faster than Guestlist can prove product-market fit.
high
Technical and platform diligence
Fix
Show signed-versus-unsigned performance on defended domains and explain the roadmap if verified traffic becomes the default lane.
Founder-market fit is promising but still under-documented for an adversarial infrastructure company.
high
Team diligence
Fix
Publish canonical founder profiles, prior relevant work, full-time status, legal entity, and the plan to cover missing reliability, legal, and go-to-market roles.
The public trust surface is thin for a service probing third-party sites.
medium
Legal and security diligence
Fix
Publish terms of service, privacy policy, acceptable-use guidance, and an opt-out or complaint workflow before scaling customer onboarding.
The standalone market may stay smaller than the excitement around the broader agent wave suggests.
medium
Market and strategy diligence
Fix
Show why the wedge expands from domain grading into routing, benchmarking, or policy intelligence with real budget ownership.

Data Room Readiness Checklist

Procurement-readiness score: not ready
Rationale: Guestlist looks like a very early self-serve developer tool today, but any serious business buyer would still ask for basic legal, privacy, security, and operating-entity materials that are not visible on the public surface.

Data Room Area	What Investors Expect	Current Read	Status	Priority
Company overview & corporate	One-pager, incorporation, good standing, structure	The product story is public, but no operating entity or structure is disclosed on the public pages reviewed here.	`partial`	high
Financials	Monthly P&L (18-24 mo), 3-yr model with assumptions, burn/runway	No public financial statements, revenue figures, or cost structure are visible.	`missing`	high
Cap table & funding history	Clean cap table, prior rounds, SAFEs/notes, 409A	No public financing history or ownership structure was surfaced for this product.	`missing`	high
Legal & IP	Bylaws, board consents, IP assignments (founders + contractors), material contracts	The public surface does not disclose terms, privacy, acceptable-use, or IP assignment posture.	`missing`	high
Product & technology	Roadmap, architecture overview, security/compliance docs	Docs and a Python package are public, but architecture, accuracy benchmark, and security posture are still private or absent.	`partial`	high
Team	Org chart, key employment/advisor agreements, vesting	One founder identity chain is visible, but background depth, full-time status, and team breadth remain thin.	`partial`	high
Customers & traction	Retention cohorts, ARR/MRR bridge, pipeline, 3-5 references	No public customer proof or retention data is visible.	`missing`	high
Market & competition	TAM/SAM/SOM, competitive landscape, pricing	The adjacent market and substitute set can be described, but Guestlist-specific pricing and a confident standalone market definition remain unresolved.	`partial`	medium

First-Call Agenda For The Startup

Time	Topic	Founder Goal	Evidence To Bring
0-5 minutes	Founder background and company status	Establish that the founder identity, full-time commitment, and operating entity are clear enough for a serious conversation.	Bring canonical public profiles, prior relevant work, incorporation details, and current company status.
5-15 minutes	Recurring-user proof	Show that Guestlist changes real routing behavior rather than serving as a curiosity tool.	Bring active-user counts, repeat-usage cohorts, and two to three concrete workflow stories.
15-25 minutes	Accuracy and signed-agent relevance	Prove that the score is trusted, current, and still useful as the access layer evolves.	Bring a benchmark with defended domains, signed-versus-unsigned comparisons, and freshness metrics.
25-35 minutes	Pricing and unit economics	Show that the product can own a budget line and does not become a financing treadmill.	Bring pricing tests, quota logic, budget-owner evidence, and cost-to-serve assumptions tied to actual probe behavior.
35-40 minutes	Team coverage and policy posture	Reduce execution and diligence-readiness risk.	Bring the plan for reliability, legal, and go-to-market coverage, plus draft or published policies.
40-45 minutes	Milestones and next gate	End with a binary decision framework rather than an open-ended watch.	Bring the next 6-12 month milestones for usage, accuracy, paid conversion, and signed-agent adaptation.

Business Model And Revenue Signals

Guestlist publicly describes itself as a free Python library and HTTP API.
Company-controlled product page.high
SourceGuestlist homepage
This is the clearest public business-model statement today.
Self-serve API-key onboarding is already live.
inferenceCompany-controlled signup page.high
SourceGuestlist signup
The onboarding motion is visible even though the post-signup product surface is not.
The public Python client is live and versioned.
source-backed factPlatform listing.high
SourcePyPI
This proves shipment, not customer dependence.
Public install proxies are low but non-zero at 0 last day, 7 last week, and 194 last month.
source-backed factPublic package-statistics site.medium
Sourcepypistats
These numbers are usage proxies for the client package, not API usage or revenue.
No paid SKU, public quota policy, or public billing surface is visible on the company pages reviewed here.
inferenceCompany-controlled product and documentation pages.high
SourceGuestlist homepage Guestlist docs
The absence of pricing is now a central fundraising gap, not a cosmetic issue.

Public revenue or profit is not available from public sources. Any revenue scenario today would still be an estimate rather than a fact.

Revenue Quality Checklist

Before this can move from hold to pursue, Guestlist should be ready to show monthly active API keys, weekly call volume, free-to-paid conversion, customer concentration, gross margin per check or monitored domain, customer acquisition cost, lifetime value, payback period, gross revenue retention, net revenue retention, and churn. Those numbers should tie out across product analytics, billing exports, the financial model, and any customer-reference packet.

Funding And Ownership Context

Item	Public Read	Evidence Label	Diligence Request
Total raised / rounds	No public financing announcement or attributable startup-database profile was surfaced for this product.	`unknown`	Share the full fundraising history, including any SAFEs, notes, or unannounced seed capital.
Instruments (equity / SAFE / notes)	No public instrument detail is visible.	`unknown`	Provide the current capitalization table and all outstanding instruments.
Investors	No public investor list is visible for this product.	`unknown`	Provide the investor roster, check sizes, and any pro rata rights already granted.
Post-money valuation	No public valuation signal is visible.	`unknown`	Provide the last priced or implied valuation and how the next round will be framed.
Cap table / ownership	No public ownership structure is visible.	`unknown`	Provide founder ownership, employee pool, and any legacy obligations.
Burn & runway	No public cash-burn or runway information is visible.	`unknown`	Provide burn, runway, and the cost profile of maintaining the probe network.
Next-round plan	No public financing plan is visible.	`unknown`	Provide the milestone plan, amount to raise, and the proof package expected to unlock that round.

Crunchbase, Companies House, and broader corporate-registry searches were checked and showed no matching operating-entity or financing record that could be tied confidently to Guestlist. These absences matter because they leave ownership, jurisdiction, and fundraising history unverified.

Founder And Team

Felix Muller appears to be the founder behind Guestlist's public launch.
The same name, email, and handle chain ties together the product surface, package maintainer, and launch post.
Guestlist homepage PyPI Hacker News Show HN PyPI user
Evidencesource-backed fact
Confidencemedium
A real product is already in market.
The founder has shipped a public homepage, signup flow, documentation hub, and Python client.
Guestlist homepage Guestlist signup Guestlist docs PyPI
Evidenceinference
Confidencehigh
The public launch footprint is extremely early.
The Show HN thread was lightly engaged, the HN account is new, and the PyPI maintainer account is also new.
Hacker News Show HN Hacker News profile PyPI user
Evidencesource-backed fact
Confidencehigh
Team depth beyond the founder is not publicly evidenced.
No second named team member or operating entity appears on the public surface reviewed here.
Guestlist homepage Guestlist docs PyPI
Evidenceinference
Confidencemedium

Founder Competency Coverage

Competency	Felix Muller	What The Evidence Is
Domain depth	`claimed`	The founder's Show HN post describes months of computer-use-agent prototyping and 40%-60% block rates, but no independent employment or project history publicly verifies that background (Hacker News Show HN).
Technical build capability	`evidenced`	A public Python package, docs surface, signup flow, and live website show real shipping ability, even though web-scale probe operations are not independently benchmarked yet (PyPI; Guestlist docs; Guestlist signup).
Product	`evidenced`	The product wedge is clearly expressed and implemented in public-facing surfaces rather than only in pitch language (Guestlist homepage; Guestlist docs).
GTM / sales	`absent`	No pricing surface, customer reference, or distribution partner is visible in public sources today.
Leadership / hiring	`absent`	No second named operator, org chart, or public hiring motion is visible in the public record today.
Fundraising history	`unknown`	No public financing history attributable to this product was surfaced.
Prior founding outcomes	`unknown`	No public prior-company outcome tied confidently to the founder identity chain was surfaced.

Continuously refreshed probe infrastructure
high
Team coverage today
Coverage today looks concentrated in one founder with no publicly evidenced operating bench.
What would close it
Show the reliability plan, vendor stack, refresh cadence, and who besides the founder keeps the system current.
Accurate adversarial scoring against evolving anti-bot defenses
high
Team coverage today
The company has documented the schema, but not the benchmark that proves the score stays predictive.
What would close it
Publish a live-domain benchmark that includes defended domains and signed-agent-sensitive cases.
Standalone value capture inside a broader access stack
high
Team coverage today
No public pricing, budget owner, or paid proof is visible.
What would close it
Show who pays, why they pay Guestlist separately, and what the paid product looks like.
Legal and trust coverage for third-party probing
medium
Team coverage today
No public terms, privacy, or acceptable-use posture is visible.
What would close it
Publish the operating entity, basic legal pages, and a site-owner complaint or opt-out process.

Public Professional Footprint

These public technical-artifact, professional-social, and credential checks carry low decision weight by design. They sharpen the founder questions below, but none of them alone changes the verdict.

Signal	Felix Muller	What The Public Record Shows
Technical artifacts (repo level)	`claimed`	The public record shows a shipped PyPI package and a PyPI maintainer profile, but no confirmed public Guestlist repository tied to the founder identity chain.
Professional social content	`claimed`	The strongest public founder narrative is still the Show HN post, which explains the problem sharply but remains self-authored and uncorroborated.
Education / credentials	`unknown`	No canonical public profile or company biography currently resolves education, location, or prior employers.
Publications / patents / certifications	`absent`	No public conference, patent, or publication trail tied confidently to the founder identity chain was surfaced in this research.

Net read: the public professional footprint is enough to support a real-builder read, but not enough to upgrade founder-market fit beyond tentative optionality.

Founder-Market Fit Read

What is promising: The founder appears close to the problem, has already shipped a live product, and framed the wedge in a way that feels more operational than generic.
What is missing: Prior depth in browser automation, anti-bot systems, or reliability engineering is still mostly narrative-level from public sources, and team coverage remains thin.
What to prepare: The founder should arrive with a canonical public profile set, references or prior work tied to the same identity chain, and a clear explanation of who covers reliability, legal, and go-to-market as usage scales.

Guestlist / guestlist-tools
The public website, package, and launch thread all point to the same early product identity chain around Felix Muller, FelixMul, and felix_myuk.
Guestlist homepage PyPI PyPI user Hacker News Show HN
Evidencesource-backed fact
Confidencemedium
Follow-upThe founder should confirm the canonical company and founder profile set.
Operating legal entity
No public operating entity or related founder company was surfaced on the public pages reviewed here.
Guestlist homepage
Confidencehigh
Follow-upThe founder should provide the incorporation record, jurisdiction, and any related entities before fundraising.

Crunchbase, Companies House, and broader corporate-registry searches were checked and showed no operating-entity record that could be tied confidently to Guestlist. This absence matters because it delays ownership, integrity, and financing diligence.

Traction

Customer Status Table

No positive customer-controlled or company-attributed customer reference surfaced in public sources.

Customer	Strongest Evidence	Customer-Controlled?	Status	Paid?	Seats	Renewal	Confidence

Guestlist, Hacker News, and Google Search were checked and showed no attributable customer logos, case studies, or references. This absence matters because it leaves workflow dependency and willingness to pay unproven.

Traction Signals

The product had a public Show HN launch, but it drew only 2 points and no visible comments.
source-backed facthigh
SourceHacker News Show HN
Guestlist still needs a second channel or repeat audience signal beyond launch-week curiosity.
The public Python client is real and recently shipped.
source-backed facthigh
SourcePyPI
The company still needs proof that the package translates into recurring API usage.
Public install proxies are low but non-zero at 0 last day, 7 last week, and 194 last month.
source-backed factmedium
Sourcepypistats
The company still needs active-user, retention, and workflow-dependency data.
The public onboarding path is live today.
inferencehigh
SourceGuestlist homepage Guestlist signup Guestlist docs
The company still needs to show that public availability turns into trusted usage and not just easy experimentation.

Hiring And Org Momentum

Signal	What Was Found	Source	Evidence Label	Interpretation

Guestlist, LinkedIn Jobs, Indeed, and Glassdoor were checked and showed no matching listing. These absences carry moderate weight because the product appears early and self-serve today, but they reinforce the public read of a very small team.

Role-mix read: No public role mix is visible, so there is no evidence yet of dedicated hiring for reliability, commercial, or policy functions.
Momentum read (growth / steady / contraction / unknown): unknown.

Traction Quality Read

Traction Dimension	Current Status	Good Enough For First Call?	Needed For Deep Diligence
External user proof	No public customer or design-partner reference is visible.	No, because the product has not yet cleared the workflow-dependency bar.	Bring recurring-user cohorts, concrete workflow maps, and at least one referenceable team.
Predictive trust	The public record shows schema and positioning, not a benchmark.	No, because a routing layer without trusted signal quality is not financeable.	Bring a benchmark on false-green rates, false-red rates, freshness, and defended-domain performance.
Pricing power	The public surface is still free-facing and does not show a paid SKU.	No, because usefulness alone does not create a budget line.	Bring pricing tests, quota logic, and evidence of separate willingness to pay.
Distribution depth	The launch signal is one low-engagement Show HN thread plus light PyPI activity.	Not yet, because the company still looks single-channel and launch-week dependent.	Bring second-channel distribution evidence and recurring usage outside the founder's network.
Team readiness	The founder appears to be the primary visible operator, with no public hiring motion.	Not yet, because the hardest build still looks undercovered.	Bring full-time status, team plan, and the roles that cover reliability, legal, and go-to-market.

Competitive Landscape

Segment	Examples	Customer Alternative	Pressure On Company
Exact direct peer	No exact direct peer was surfaced in this public search set.	Customers can still ignore the distinction and buy a broader stack.	Novelty alone does not prove category ownership; it can also mean the wedge is too narrow or too young.
Execution-layer substitutes	Browserbase, Bright Data Web Unlocker, Firecrawl, and TinyFish	Customers can attempt the browser, unlocker, or crawl step directly inside a broader tool and accept the cost of failed tries.	These vendors already own the budget and workflow Guestlist wants to influence.
Defense-side incumbents	Cloudflare Bot Management, plus the WAF vendors Guestlist names on its own site	Site owners can keep tightening bot defenses or prefer authenticated traffic.	These players can change the environment Guestlist must measure faster than Guestlist can explain the shift.
Manual fallback workflow	Retries, proxies, and debugging inside the existing stack	Teams can treat access failure as a cost of doing business instead of buying another tool.	If customers do not feel enough pain, Guestlist stays a convenience rather than a control point.

Category Visibility Snapshot

Google Search / USAI agent website access preflight API anti-bot

Captured page-one results (2026-06-25): Unbrowse, AlterLab, Fast.io, TinyFish, Bright Data, and developer-forum results appeared on the reviewed first page.
Was the company present?: no

Google Search / GBAI agent website access preflight API anti-bot

Captured page-one results (2026-06-25): Unbrowse, AlterLab, Fast.io, TinyFish, Bright Data, Browser Use, and Imperva-related results appeared on the reviewed first page.
Was the company present?: no

Google Search / USsite:guestlist.tools

Captured page-one results (2026-06-25): Guestlist's homepage was the only indexed result visible on the reviewed first page.
Was the company present?: yes

Google Search was checked in the United States and the United Kingdom for category terms, and Guestlist did not appear in the reviewed page-one category results. This absence matters because it suggests the company has not yet won discoverability for its own wedge.

Visibility read (inference, low confidence): Guestlist currently has almost no category-level share of voice. Discovery is still dominated by broader stacks, listicles, and defense-side content rather than by Guestlist itself.

Pricing And Competitive Benchmark

Alternative	What It Offers	Public Price Signal	Price Vs. This Company	Evidence Label
Browserbase	Managed browsers, fetch, search, and agent-identity tooling.	Browserbase shows a free tier, paid browser-hour plans, and fetch pricing from $1 per 1,000 calls on its public pricing page.	Guestlist's public surface remains free, which helps adoption but still says nothing about whether it can later charge against a broader execution stack.	`company claim`
Bright Data Web Unlocker	Anti-bot unlock and scraping infrastructure at request time.	Bright Data shows a free tier, PAYG pricing of $1.50 per 1,000 successful requests, and a $499 monthly scale plan.	Guestlist looks cheaper today, but Bright Data already owns a paid budget at the point of execution.	`company claim`
Firecrawl	Agent-oriented scrape, crawl, and extract tooling.	Firecrawl shows a free tier and a $599 monthly scale plan for higher-volume teams.	Guestlist undercuts the sticker price today only because it has not yet published a paid product.	`company claim`
TinyFish	Search, fetch, and stealth browser sessions for web agents.	TinyFish shows PAYG pricing at $0.015 per credit, plus paid plans starting at $15 per month.	TinyFish is closer to Guestlist's likely buyer and already packages anti-bot outcomes, which raises the bundling risk materially.	`company claim`

Price positioning read: Guestlist currently wins the sticker-price comparison because the public product is free. That is a useful adoption wedge only if the company later proves that the signal is valuable enough to charge for.
Price claims to correct or substantiate: Before fundraising, Guestlist should explain what remains free, what becomes paid, and why customers will not simply demand a bundled pre-check from a broader vendor they already pay.

Competitive Wedge

The defensible version of Guestlist is a neutral pre-flight signal that works across multiple access vendors and agent stacks, not a thin wrapper around any single browser or unlocker platform. In that version, the company wins because customers trust the score, route meaningful spend through it, and see the dataset improving with usage.

The current public record does not yet prove that version. What it shows instead is a sharp wedge surrounded by better-capitalized substitutes and a defense-side market that can redefine access standards faster than Guestlist has yet shown it can adapt.

Risks And Open Questions

Risk	Severity	Evidence	What To Ask
Guestlist may never become a standalone budget line.	high	Adjacent stacks already price the workflow, while Guestlist's public surface remains free-facing (Browserbase pricing; Bright Data pricing; Firecrawl pricing; Guestlist homepage).	Ask who pays, why they pay separately, and what happens if the same feature appears inside the broader stack they already buy.
The score may not be predictive enough to trust.	high	The public record documents the schema and the pitch, but no benchmark on false-green rates, false-red rates, or freshness is public (Guestlist docs; PyPI).	Ask for a live-domain benchmark with defended sites, error rates, and refresh discipline.
Authenticated-agent standards may move the battleground away from Guestlist's current probe model.	high	Cloudflare's authenticated-agent push is real and public (Cloudflare Web Bot Auth; Cloudflare signed agents).	Ask how Guestlist performs when real customer traffic is signed or otherwise identity-verified.
Founder and team coverage are thin for an adversarial infrastructure company.	high	A shipped product is visible, but founder background and team breadth remain only partly evidenced (PyPI; PyPI user; Hacker News profile).	Ask what the founder built before this, whether Guestlist is full time, and who owns reliability, legal, and go-to-market.
The legal and policy surface is underbuilt.	medium	Public onboarding and documentation are visible, but no public trust or policy surface accompanies them on the public pages reviewed here (Guestlist homepage; Guestlist docs).	Ask for the entity, terms, privacy posture, acceptable-use guidance, and site-owner complaint or opt-out process.
The standalone market may remain narrow even if the product is useful.	medium	The adjacent price corridor is real, but a client-safe standalone market-size source never surfaced and the broader stacks remain much larger (Browserbase pricing; Bright Data pricing; Firecrawl pricing).	Ask how the company expands from domain grading into a broader routing, benchmark, or policy layer with real budget ownership.

Pre-Mortem: The Most Likely Obituary

Cause of death (one sentence): Guestlist dies because its pre-flight score never becomes a trusted, budget-owning workflow dependency before larger browser, unlocker, and authenticated-agent platforms absorb or redefine the same decision point.
The causal chain (3-5 steps from today to the shutdown): Early users find the product clever, but not essential; the company never publishes a benchmark strong enough to make buyers trust it in production; authenticated-agent lanes make unsigned probes less representative of real customer traffic; broader access vendors ship a good-enough bundled pre-check; and Guestlist ends up useful without pricing power, margin leverage, or durable ownership of the workflow.
The earliest observable warning sign: The next founder conversation still cannot produce one external team that both depends on the score in a repeat workflow and would pay for it separately if a broader access platform offered a bundled version.
The question that defuses this chain today: What proof can the founder show that Guestlist changes real routing behavior, stays predictive as access standards evolve, and commands incremental budget on top of the tools customers already buy?

Decision-Critical Unknowns

Unknown	Why It Is Decision-Critical	Best Evidence	Decision Effect
Recurring external users and workflow placement	This is the fastest test of whether Guestlist is a workflow dependency or a curiosity tool.	The best evidence would be referenceable users, retention by cohort, and workflow maps that show where Guestlist changes routing decisions.	If this remains thin, the case drifts from hold toward pass.
False-green rates, false-red rates, and freshness discipline	The company cannot be financed as a reliability layer without trusted signal quality.	The best evidence would be a benchmark on live domains with defended-domain cases and clear update cadence.	Strong results move the case toward pursue; weak or missing results move it toward pass.
Signed-agent relevance	The largest visible standards shift may make the current probe shape less representative of real customer traffic.	The best evidence would be signed-versus-unsigned comparisons on Cloudflare-heavy or similar defended domains.	If the signal breaks under authenticated traffic, the wedge may already be structurally misaligned.
Pricing and unit economics	Usefulness without budget ownership is not enough for venture underwriting.	The best evidence would be live or tested pricing, budget-owner evidence, and a cost model tied to real probe behavior.	If the founder cannot show separate willingness to pay, the value-capture case weakens sharply.
Founder background, full-time status, and operating entity	The founder is still the asset here, and the company is not yet legible enough for serious diligence.	The best evidence would be canonical profiles, prior relevant work, references, and incorporation details.	If the identity and company setup remain thin, confidence stays capped even if the product is technically interesting.
Coverage breadth and `unknown` share	A routing layer with too much uncertainty or too little freshness does not compound into a moat.	The best evidence would be coverage statistics, the distribution of `unknown` results, and evidence that usage improves the graph.	If coverage remains thin, the long-horizon moat thesis stays speculative.

Diligence Questions

First Call

Question	Why It Matters	Good Evidence
Who are the first recurring users or design partners, and where exactly in their workflow does Guestlist change a routing decision before they spend browser time or unlocker budget?	This tests workflow dependency and buyer reality in one step.	Good evidence is a set of referenceable or de-identified recurring workflows with usage depth and a clear before-versus-after decision point.
What are today's false-green rates, false-red rates, `unknown` rates, and freshness metrics on a live-domain panel?	This tests whether the core signal deserves trust.	Good evidence is a benchmark with methodology, defended-domain cases, and clear update cadence.
How does Guestlist behave when the real customer workflow uses signed or authenticated agent traffic instead of unsigned probes?	This tests whether the product is aligned with the direction of the market.	Good evidence is A/B data on authenticated versus unauthenticated flows and a clear roadmap response.
What is the monetization plan right now, including price tests, quota policy, buyer, and cost to serve?	This tests whether Guestlist can own a budget line before broader vendors bundle the feature.	Good evidence is real pricing or price-test data, budget-owner evidence, and a cost model tied to actual usage.
What did the founder build before Guestlist, and is the company full time with a credible plan to cover reliability, legal, and go-to-market gaps?	This tests founder-market fit and execution capacity.	Good evidence is a canonical profile set, prior relevant work, references, full-time status, and a concrete coverage plan.

Follow-Up

Question	Why It Matters	Good Evidence
How large is the active graph today, how fast is it refreshed, and how much of the value comes from usage-linked improvement versus scheduled re-probing?	This tests whether the proposed moat compounds or just becomes more expensive to maintain.	Good evidence is coverage breadth, refresh cadence, and evidence that more usage improves the graph rather than only costs more.
Why do customers buy Guestlist separately instead of demanding the same feature inside Browserbase, Bright Data, Firecrawl, or TinyFish?	This tests bundling resistance and category independence.	Good evidence is customer rationale for a neutral layer and examples of multi-stack deployments.
What legal and site-owner posture governs the probe network?	This tests whether policy debt can become a fundraising or enterprise blocker.	Good evidence is a published or near-final terms, privacy, acceptable-use, and opt-out package.
What 12-month milestones would make the next round easy rather than merely possible?	This tests whether management knows what evidence actually unlocks financing.	Good evidence is a milestone plan tied to usage, pricing, accuracy, freshness, and signed-agent adaptation rather than vanity launch metrics.

Kill Criteria

Kill Criterion	Evidence That Would Trigger It
The score does not predict live customer outcomes with enough accuracy to change workflow decisions.	A benchmark shows weak lift, high false-green rates, high false-red rates, or freshness that decays too quickly to matter.
Authenticated-agent traffic makes Guestlist's current probe model materially misleading on important defended domains.	Signed-versus-unsigned testing shows the score no longer maps to the traffic pattern serious users actually run.
Buyers only want the capability bundled into broader browser or unlocker tooling.	Customer interviews and pricing conversations show no one will allocate separate budget to Guestlist.
No recurring external users exist beyond founder self-use or shallow experimentation.	Usage and customer proof still cannot show even a few repeat workflows with real operational dependence.

Double-Down Criteria

Double-Down Criterion	Evidence That Would Justify More Diligence
The signal is demonstrably trusted.	A live-domain benchmark shows disciplined false-green rates, false-red rates, freshness, and defended-domain performance.
The product is already becoming part of a real workflow.	Three or more recurring external teams use Guestlist repeatedly in routing or fallback decisions.
A separate budget line is forming.	Pricing tests or paid design-partner behavior show a buyer who will pay on top of existing access-stack spending.
The moat is compounding rather than decaying.	Usage-linked evidence shows coverage, freshness, and confidence improve as the graph grows.

Founder Action Plan

Timeframe	Action	Output
Before the next investor call	Package recurring-user proof, including active usage, retention, and two to three concrete workflow stories.	A usage and dependency packet that proves Guestlist changes real routing decisions.
Before the next investor call	Run a benchmark on live domains, including defended domains and signed-agent-sensitive cases where possible.	An accuracy and freshness packet with error rates, cadence, and representative examples.
Before the next investor call	Turn the free-facing product into a legible commercial story with price tests, quota logic, and budget-owner evidence.	A pricing and unit-economics memo tied to actual probe behavior.
Early diligence	Publish or privately share the founder background, full-time status, legal entity, and coverage plan for reliability, legal, and go-to-market roles.	A founder and company readiness packet.
Before broader fundraising	Publish terms, privacy, acceptable-use, and site-owner complaint or opt-out guidance.	A trust and policy package that reduces diligence friction.

Decision

Screen: hold
Confidence: medium
Rationale: Guestlist has a sharp wedge, a real product surface, and a plausible upstream role in a growing agent-access stack, but the public record still does not prove repeat workflow dependency, predictive trust, signed-agent resilience, or standalone value capture.
What would move this to pursue: A credible proof packet showing recurring users, strong benchmarked signal quality, signed-agent relevance, early paid intent, and a founder or company profile sturdy enough for deeper diligence.
What would move this to pass: Weak or missing benchmark data, no recurring external users, no separate willingness to pay, or evidence that authenticated-agent lanes and broader stacks already own the real control point.
Recommended next step: Take one time-boxed founder call only after the proof packet is shared in advance, and otherwise keep the company on a short watch rather than drift into open-ended curiosity.
Founder preparation standard: The founder should treat the next investor conversation as a proof meeting, not a narrative meeting.

How We Would Miss This One

The miss scenario: We would miss Guestlist if the company is much earlier than the public record can show, the benchmark turns out to be strong, and a few real teams are already using the score as routing infrastructure before the broader market notices.
Flip conditions: A benchmark that shows strong predictive value, three or more recurring external teams using the product in repeat workflows, a clear paid budget owner, and a founder background packet that proves unusual fit for this wedge would all move the case materially.
Revisit trigger / date: Revisit immediately if the founder shares that proof packet, or by 2026-09-25 if new public evidence on usage, pricing, or signed-agent adaptation appears before then.

Source Log

Guestlist homepage
guestlist.tools
This page supports Guestlist's public positioning, free-facing product surface, and named blocker vendors.
Retrieved 2026-06-25company-controlled product page (Guestlist)high
Guestlist docs
guestlist.tools
This page supports the documented tier system, API schema, blocker labels, and apex-domain limitation.
Retrieved 2026-06-25company-controlled technical documentation (Guestlist)high
Guestlist signup
guestlist.tools
This page supports the existence of live self-serve API-key onboarding.
Retrieved 2026-06-25company-controlled signup page (Guestlist)high
guestlist-tools on PyPI
pypi.org
This page supports the release date, version number, MIT client license, and maintainer metadata.
Retrieved 2026-06-25platform listing (PyPI)high
guestlist-tools on pypistats
pypistats.org
This page supports the public install proxy of 0 last day, 7 last week, and 194 last month.
Retrieved 2026-06-25public package-statistics page (pypistats)medium
Hacker News Show HN thread
news.ycombinator.com
This page supports the public launch, the founder's narrative, and the low-engagement launch signal.
Retrieved 2026-06-25public community page (Hacker News)medium
Hacker News user profile felix_myuk
news.ycombinator.com
This page supports the founder handle, account age, and low public footprint on Hacker News.
Retrieved 2026-06-25public profile page (Hacker News)high
PyPI user FelixMul
pypi.org
This page supports the maintainer handle and its recent account creation date.
Retrieved 2026-06-25public maintainer profile (PyPI)high
Gartner agent-adoption forecast
gartner.com
This page supports the parent-category timing signal for task-specific agents.
Retrieved 2026-06-25analyst press release (Gartner)high
Anthropic computer-use documentation
platform.claude.com
This page supports that computer-use behavior is already productized at a major model platform.
Retrieved 2026-06-25platform technical documentation (Anthropic)high
Bright Data Web Unlocker pricing
brightdata.com
This page supports adjacent unlocker pricing and the existence of paid web-access infrastructure budgets.
Retrieved 2026-06-25competitor pricing page (Bright Data)high
Browserbase pricing
browserbase.com
This page supports adjacent browser-agent pricing and public execution-layer budget anchors.
Retrieved 2026-06-25competitor pricing page (Browserbase)high
Firecrawl pricing
firecrawl.dev
This page supports adjacent agent web-data pricing and another public budget anchor.
Retrieved 2026-06-25competitor pricing page (Firecrawl)medium
Browserbase homepage
browserbase.com
This page supports Browserbase as a broad substitute in the same buyer corridor.
Retrieved 2026-06-25competitor product page (Browserbase)high
Firecrawl homepage
firecrawl.dev
This page supports Firecrawl as a broad substitute in the same buyer corridor.
Retrieved 2026-06-25competitor product page (Firecrawl)high
TinyFish homepage
tinyfish.ai
This page supports TinyFish as a broad substitute in the same buyer corridor.
Retrieved 2026-06-25competitor product page (TinyFish)high
TinyFish pricing
tinyfish.ai
This page supports TinyFish's public pricing and bundling pressure.
Retrieved 2026-06-25competitor pricing page (TinyFish)high
Cloudflare Bot Management
cloudflare.com
This page supports the defense-side incumbent pressure in Guestlist's market.
Retrieved 2026-06-25incumbent product page (Cloudflare)high
Cloudflare Web Bot Auth
blog.cloudflare.com
This page supports the shift toward cryptographically verified agent traffic.
Retrieved 2026-06-25platform blog (Cloudflare)high
Cloudflare signed agents
blog.cloudflare.com
This page supports the signed-agent program and the strategic importance of authenticated traffic.
Retrieved 2026-06-25platform blog (Cloudflare)high
Cequence: AI agents are bots
cequence.ai
This page supports that anti-bot systems already detect and block agent-like behavior using behavioral signals.
Retrieved 2026-06-25vendor field report (Cequence)high
Polsinelli hiQ scraping update
polsinelli.com
This page supports that public-data scraping may fall outside CFAA exposure while terms-of-service risk can still remain.
Retrieved 2026-06-25legal analysis (Polsinelli)medium
EFF commentary on hiQ
eff.org
This page supports the narrower CFAA interpretation for scraping public data.
Retrieved 2026-06-25legal commentary (EFF)medium
Browserbase on Crunchbase
crunchbase.com
This page supports Browserbase's employee band and financing rounds as a public comp.
Retrieved 2026-06-25startup database (Crunchbase)high
TinyFish on Crunchbase
crunchbase.com
This page supports TinyFish's employee band and financing rounds as a public comp.
Retrieved 2026-06-25startup database (Crunchbase)high
Fast.io AI browsing tools listicle
fast.io
This page supports Guestlist's current omission from a public comparison list in the category.
Retrieved 2026-06-25third-party listicle (Fast.io)medium

Access limitations: Several decision-critical items remain unavailable from public sources. No public customer references, pricing page, legal-entity disclosure, or benchmark on signal quality were surfaced, and the founder's deeper background is still only partially confirmed. Search-result checks and inaccessible policy pages informed the absence read, but they are not included in the Source Log because they are not reliable client-facing citations. Those gaps are exactly why the verdict stays at hold rather than moving toward pursue.

Public disclaimer: This is an independent public teardown based solely on publicly available information retrieved on 2026-06-25. It is research support, not investment, legal, tax, or financial advice. Company-provided statements are labeled as claims, not verified facts. Guestlist did not participate in or review this report. Errors and omissions are possible; final decisions remain with the reader.

What The Company Does#

Key Takeaways#

What Makes This Potentially Fundable#

The Four Holes To Close Before Fundraising#

Decision Snapshot#

IC Disagreement Map#

Scenario Range#

What Investors Will Test#

Claim Reconciliation: Inconsistencies Investors Will Catch#

Diligence Findings: Issues To Fix Before You Raise#

Data Room Readiness Checklist#

First-Call Agenda For The Startup#

Business Model And Revenue Signals#

Revenue Quality Checklist#

Funding And Ownership Context#

Founder, Team, And Related Entities#

Founder And Team#

Founder Competency Coverage#

Public Professional Footprint#

Founder-Market Fit Read#

Related Entities And Founder-Associated Companies#

Traction#

Customer Status Table#

Traction Signals#

Hiring And Org Momentum#

Traction Quality Read#

Competitive Landscape#

Category Visibility Snapshot#

Pricing And Competitive Benchmark#

Competitive Wedge#

Risks And Open Questions#

Pre-Mortem: The Most Likely Obituary#

Decision-Critical Unknowns#

Diligence Questions#

First Call#

Follow-Up#

Kill Criteria#

Double-Down Criteria#

Founder Action Plan#

Decision#

How We Would Miss This One#

Source Log#