Anon and Invisible — Product Info Sheet (8/1/23)

Anon and Invisible — Product Info Sheet (8/1/23)

Quick Context / Background

  • Daniel Mason (Anon) was introduced to Saranna Biel-Cohen (Invisible) by an early investor in Anon. Saranna then introduced Daniel to Chris Chavez (Invisible).
  • Daniel Mason spoke with Chris Chavez (Invisible) about Anon’s authentication and access management solution, as either a replacement for Invisible’s current vendor, LastPass, or as an SDK / developer toolkit that could help Invisible build out it’s own proprietary access management system.
After considering Invisible’s use cases, we believe that our SDK product (versus our Standard Product) is probably the better option. Our Standard Product is built as an authentication and access management system to replace password managers for virtual assistant services. Our SDK Product has no UI/UX and is instead a set of APIs and services that can be built into a customer solution to serve Invisible’s scale and unique needs. This product is also very differentiated from traditional password managers which offer minimal customization options for Invisible’s use cases. Our Standard Product is simply a standard UI/UX built on top of the SDK Product.
For clarity, we use the following terms throughout: - Invisible VAs when talking about virtual assistants / outsourcers working for Invisible. - Invisible Admins when talking about FTEs at invisible that oversee operations.

Company Overview and Product

What is Anon?

  • is an early-stage technology company building a developer SDK for authentication and access management that enables identities to be securely shared with granular controls and auditability.
  • With our solution, an Invisible VA can request control of a client account (e.g. LinkedIn), and the client can grant access without ever sharing a password. This improves security, control, and user experience for clients.
  • Additionally, our solution provides "admin" privileges to Invisible Admins, allowing them to manage, revoke, or transfer account access between team members at any time, as well as see an audit trail of what team members did while accessing a service.
  • Anon replaces tools like shared password vaults or links that weren’t designed for multi-user commercial use, reinventing client onboarding and access management.

Anon Product Demo

  • The following product demo is a walkthrough of our Standard Product, which is effectively a UI/UX built on top of our SDK product. The demo is short but intended to show the basic functionality which can be extrapolated to many use cases.
  • This specific use case shows a virtual assistant (Hannah) at a fictional company ( requesting, then receiving access to a United Airlines account from her client (Jose):

While our product is only in Alpha today, this demo shows real screens from the product. This will be available for a full external demo to Invisible in the coming weeks.

Value Proposition and Competitive Positioning

Why Password Managers are Insufficient

  • Password managers were built for a different job. LastPass and 1Password are designed for single users, or organizations comprised of single users, but have been adapted over time to add features like password sharing.
  • Fundamentally, these tools only work client-side, meaning a shared password is necessarily shared in plain text with the recipient for it to work. This isn’t a flaw with 1Password, or with LastPass, but rather a flaw with the entire paradigm of password sharing, as it exists today.
  • For individuals or most organizations, 99% of password management use cases are “single player.” Occasionally colleagues may share a seat on Salesforce, or your friend uses your Netflix, but these are edge cases, not the standard use of the product.
  • The reverse is true for Invisible. Multi-user access sharing is the standard, not an edge case. This “multiplayer” functionality is necessary for the business to operate.
  • This is why password managers work for many companies, but are ill-adapted to multiplayer-first use cases like outsourcing, virtual/executive assistants, AI agents, BPO, and more.

Specific issues with password managers for Invisible are:

  • 🔓 Shared passwords are unlikely to be hacked because of encryption on servers, but fully visible locally, making password vaults only marginally safer than text/email for sharing.
  • ⛔ There is no way to “revoke” credentials, meaning an Invisible VA that is negligent, reckless, or gets fired puts the client at risk unless the client changes all passwords.
  • 🔀 There is no way to “transfer” access with password managers. A vault can be re-assigned, but the new Invisible VA still has to login (and get 2FA codes) with each new client.

Anon: A First Principles Reinvention of Password Sharing

  • Anon is not a password manager with a better UI. Instead, we are a fundamentally new way to think about access sharing. From a technological standpoint, we facilitate sharing of cookies and session tokens instead of passwords.
  • This password-less sharing paradigm is safer, provides more control, and improves the experience of access management for Invisible, and Invisible’s customers.

Specific advantages of Anon’s approach to access management include:

  • ♻️ Reduce back-and-forth for 2FA codes during initial authentication and re-authentication of services, especially during client onboarding or re-assignment to a new outsourced team member.
  • 🎮 Improve access control and auditability including the ability to revoke or transfer existing access and the ability to have an auditable log of all past and current access permissions.
  • 🔒 Maintain compliance for the Invisible team as well as security-conscious clients and those with HIPAA, PCI, or SOC 2 compliance standards.
  • 🤖 Improve security around AI adoption by creating a credential management process that works for AI agents that need to access data or take actions online.
  • 🔌 Access configurable APIs that Invisible can use in building its own custom access management solution, versus buying a commodity product built for a different use case.
  • 🥇 Reinforce reputation as the obvious choice among outsourcing solutions for security, user experience, and tech-enablement.

Example Use Cases for Invisible

  • Outline of two potential use cases for access sharing with Invisible VAs:
    1. Product Onboarding
    2. Lead Generation

Product Onboarding

  • An example is processing SKUs for a large eCommerce retailer.
  • This might include Invisible VAs accessing multiple sites or backend systems using a single login to gather product images, descriptions, and other information to onboard a new product to the retailer’s website.
  • Anon could reduce friction with shared accounts and provide real-time visibility and access controls for Invisible VAs using shared accounts.

Lead Generation

  • Another example is creating lead lists.
  • In this use case, multiple Invisible VAs would be able to utilize a single client LinkedIn or ZoomInfo (or Redfin, Zillow, etc.) account and search for contacts to add them to a CRM.
  • Anon could improve the user experience by reducing 2FA requests to the end-user, and by making 2FA asynchronous (and on the client’s device, instead of requiring back-and-forth communication).
  • From a security and compliance standpoint, this would also eliminate the need to send sensitive account credentials to Invisible VAs.

Next Steps for Invisible and Anon

Design Partnership

  • While there is still a lot of additional information to provide, we would love to work towards a design partnership between Anon and Invisible.
  • Under this partnership, we would closely partner to co-design Invisible’s new access management solution, which would be built using APIs provided via Anon’s SDK Product.
  • The goal of the design partnership would be for Invisible to gain access to our software at an extremely favorable rate in return for being an early customer of Anon and providing us feedback that enables us to improve our product for the future.

Product Demo

  • We are close to being able to deliver a product demo to Invisible, and are glad to schedule this for a few weeks out to show you how our product functions, both at the technology and SDK level, as well as within the full UI/UX we are building for virtual assistant providers.

Product Questions for Scoping

  • We would want to put together a list of questions for a future meeting to review with the team at Invisible to give us the information we would need to fully understand your use cases and propose a solution.
  • We are obviously glad to go under MNDA in advance of this meeting.


More Info About

What is is an early-stage technology company building an access management solution that enables identities to be securely shared with granular controls. We are building this solution primarily for BPO companies, EA/VA services, and autonomous AI agent startups.

Our vision is to create a more secure identity layer that connects users and companies. This layer will help businesses like Invisible improve security and access control today and will also enable Invisible to scale with AI or hybrid agent solutions in the future.

The Team is a 7-person team based in Los Angeles, CA.

The company was founded by three co-founders: Daniel, Peter, and Kai with deep background building companies in the security, AI, and financial services sectors. Collectively we have raised >$100mm for past companies, and have raised $2mm to-date for, with more financing closing in the coming months.

The remainder of the team is heavily technical and product-oriented, with 2 software engineers with backgrounds at Amazon, Meta, and Stability AI, and 2 product/design-focused team members both from Cash App / Square.

Founder Backgrounds


Daniel Mason


  • Previously was Partner at Framework Ventures, a $1.1B venture capital fund based in San Francisco.
  • Before that co-founded Spring Labs, a security startup with $68mm in funding that provides security solutions to large institutions like TransUnion, GM Financial, Amount, and more.


  • Previously COO at TeamPay, a $175mm payments startup based in New York.
  • Before that served on the executive team at, worked in Private Equity at Carlyle Group, and served as an Intelligence Officer in the US Army.


  • Previously was Chief Technology at Alaffia, a Series A AI/ML Healthtech startup in New York.
  • Before that worked in engineering at Goldman Sachs and Amazon after graduating from MIT.