Athena Proposal (7/11/23)

Athena Proposal (7/11/23)

Engagement Overview and Value Proposition

What is Anon?

  • is an early-stage technology company building an access management solution that enables identities to be securely shared with granular controls.
  • Using our solution, an EA can request control of a client account, and that client can provide access without ever sharing a password. This improves security, control, and UX for clients. It also provides “admin” privileges to the EA service, which can manage, revoke, or transfer account access at any time.
  • Anon replaces tools like shared password vaults or links that weren’t designed for multi-user commercial use, reinventing client onboarding and access management with new technology that is a win-win for EA services and their clients.

Engagement Goals

  • To create a simple way for Athena to improve client onboarding, authentication, and security, with the aim of boosting sales, reducing client churn, and enabling Athena to explore AI augmentation of existing services.

Benefits to Athena (and Athena’s Clients)

  • 🔒 Ability to sell into new verticals, including security-conscious clients and those with HIPAA, PCI, or SOC 2 compliance standards.
  • ♻️ Reduced back-and-forth for 2FA codes during initial authentication and re-authentication of services, especially during client onboarding or re-assignment to a new EA.
  • 🎮 Improved access permissions control including the ability to revoke or transfer existing access without the client needing to do manual work.
  • 🤖 Improve security around AI adoption by creating a credential management process that works for AI agents that handle client credentials to access data or take actions online.
  • 🥇 Reinforcement of reputation as the obvious choice among EA services for security, user experience, and tech-enablement.
    • From Chris and I’s first conversation, a partnership could be accompanied by a PR push targeting startup founders and technology executives:
    • Athena further bolsters its reputation of being the most technological and security-minded EA service by integrating Anon, the leading trustless access sharing platform.

Anon vs. Password Management Software Today

Tools like 1Password are designed for a single user to store passwords, but they have been adapted to handle credential sharing between clients and EAs. This creates security challenges and friction in accessing the accounts of your clients.


  • 🔓 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 EA that is fired or re-assigned still has access to all client accounts unless he/she changes all passwords.
  • 🔀 There is no way to “transfer” access with password managers. A vault can be re-assigned, but the new EA still has to login (and get 2FA codes) with each new client.

Proposed Agreement Outline

Overall Structure

  • We propose a design partnership between Anon and Athena. This agreement would ensure that Anon delivers software to Athena that meets an agreed-upon set of requirements in return for Athena providing expertise, and feedback to enable us to create a better product.
  • Anon would also provide Athena a significant (50%+) “Design Partner” discount on a future software license agreement.

Anon Software Requirements

  • We should collectively define the final structure of the deliverable software, but our initial recommendation would be:
    • Access management dashboard that enables Athena EAs to manage access to a pre-set list of mutually-decided apps and services across all client accounts. This would enable requesting, revoking, and transferring account access. It would also enable Athena admins to add, remove, and manage EAs to streamline onboarding/off-boarding.
    • Access link sharing and auth product built into the dashboard that enabled EAs to request access via any form of communication (text, email, Slack, etc.) and enabled Athena clients to complete authentication and 2-factor authentication.

Athena Partner Requirements

  • Athena would be responsible for consistent product feedback to the Anon product team to inform the development and deployment of a software product that fits the needs of Athena, including Athena admins, EAs, and clients.
    • Athena would provide data on common services shared with EAs such that we could develop a pre-set list of apps and services available at launch.
    • Athena would provide client feedback data, including operational data like sales data, churn data, customer satisfaction data, etc. such that Anon can continue to improve our product offering.
  • Athena would pay Anon for the software, with some minimum commitment, at a discounted “Design Partner” rate.
    • Our ideal would be to charge a portion of a “security and access management software” line item / upsell to Athena clients. The aim is that this expands Athena’s software revenue, more than paying for Anon’s product.
    • We would want feedback from Athena on pricing, but estimate that Athena add a $25-$50+/month/client software package, with Anon taking $15/client/month, discounted an additional 50% to $7.50/month/client as a “Design Partner”.
Ultimately, we want our pricing to be based on value creation. We believe Athena can upsell clients on software that makes their lives better, providing time savings, increased control, and better security, and that Anon can share that upside with Athena.
Anon is an early-stage company and would plan to invest significant resources at a steep discount for Athena as a design partner, so we would ask for a 3-6 month commitment from Athena, contingent on Anon meeting agreed-upon SLAs and design requirements.

Questions to Discuss

  • 🖥️ Product
    • Which client services or applications are top-of-mind for Athena to support from day 1? (i.e. what are the credentials that are most actively shared among Athena clients and EAs?)
    • Would Athena want to create a standardized “onboarding page” where clients can delegate access to all services in a single interface or prefer to handle authentications on an “as needed” basis?
  • 🏦 Pricing
    • Does Athena think that a “security and authentication” upsell for delivering software that makes clients’ lives easier is feasible? If so, how much might that be worth to clients?
    • What security products do Athena clients (or Athena itself) buy today that could be bundled into a more cohesive security and authentication product?
  • 📈 Sales and Support
    • At the last startup I co-founded, Spring Labs, I had to get rid of my VA when we got our Soc 2 compliance; however, different organizations might interpret the “no password sharing” mandate differently. Has Athena come across this in sales to certain verticals? Or are there workarounds that have worked to help Athena sell into these organization?
    • What metrics has Athena seen with regards to client NPS or churn during periods of transition such as when Athena re-matches an EA (due to better fit, termination, resignation, etc.)
  • 🤝 Startup partnerships
    • We designed a structure that we thought could make sense for both Athena and for Anon; however, have you designed engagement structures with startups previously that have worked especially well?
      • [Talked a bit about with Ben but curious for other examples]

Proposed Next Steps

  1. Meet to review this document. We have time with Chris scheduled for Thursday (7/13/23).
  2. Coming out of that meeting, we can make adjustments to the structure or add specifics based on feedback or answers to the outstanding questions.
  3. Once we’re aligned, we can go under MNDA for final information gathering and to finalize a scope for the design partnership.
  4. Once that is complete, we can get started!

We’re excited about the potential here and will look forward to speaking and reviewing this document with you soon.




How the Software Works

We would love to do a full review of our technology with Athena’s engineering team; however, below is an example of how an access management flow between a Athena VA (Hannah) and a client matched using Athena’s one-to-one VA matching service (Jose) would work.


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 EA/VA services and companies building AI agents.

Our vision is to create a more secure identity layer that connects users and companies. This layer will help businesses like Athena improve security and access control today and will also enable Athena 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.