tyrw

I read the parent comment as "If I go to a 60 year old and present them a non-excel build, they will ask me why didn't I just use excel?"

Thank you! That's such a strange place to put it. Silly me, looking on the "Settings" > "View options" page instead of the button that says "Week".

Edit: doesn't look like there is the equivalent option on mobile, so unfortunately appointments still nukes my phone calendar usability, which is also a deal breaker.

We really wanted to use this, but having an appointment link creates a permanent vertical "event" in your own calendar that you can't get rid of. So adding multiple appointment links (e.g. one for 30mins and one for 60mins) completely destroys your own calendar view.

Clerk is great for new builds in the react ecosystem. We focus on more complex use cases where there are multiple user types (e.g. freemium, enterprise, partner, internal), multiple applications, or both. Having everything in one system removes a lot of tech debt and helps teams move faster.

And by "happy to chat" I meant by my email in my bio (which I just added to the public part), if it'd be helpful!

Depends on the app and the context. A lot of apps need multi-tenant access control but not necessarily separate containers etc. In those cases, "adding" multi-tenancy means maintaining an Organizations table, a Roles table, and a table to map them to Users.

Sorry I got busy today (more convos!). I'd be happy to chat or email and try to be helpful -- if you want you can check my bio.

We build a system that is multi-tenant capable but can run as single tenant until you need it. Happy to chat if helpful

> Large companies didn’t want it enough to deal with our lack of “big company features” (enterprise SSO, compliance certifications...

> We spent a bunch of time on multi-tenant infrastructure...

I'm in a position where I talk to SaaS businesses all day about both of these. Probably over 1,000 at this point.

We help a lot of these companies add the enterprise features they need, but it's often a shame to hear they're just going to do standard login or build multi-tenancy themselves. Trying to sell to enterprises without meeting them where they are on login & compliance is asking for failure.

I think a lot of founders and early employees are true believers in their value prop, and in this case it blinds them to the fact that there are people in the world like enterprise CSOs who simply don't care and will shut down a product for any number of security reasons. You have to check the boxes, and figuring out what those boxes are on the fly is painful and costly.

Balsamiq is already so cheap. We use it for our business and every time it renews I just think they could be getting 5-10x what they are. That in turn helps drive a better business and product.

It feels like there is an analogy here with Yahoo! and the early days of going from curated lists of websites to search algorithms. Do you think of LLMs in a similar way? I.e. some kind of model ranking score that companies could eventually game?

I'm not sure what the SEO equivalent would be here...

We're required to have code review as part of our SOC2 process, and I assume automated agents wouldn't count.

The other end of the spectrum is linting and tests, which catch errors before review.

Does Ellipsis have a role between these two? If so, what is the role?

This looks like a nice project, though it's a tricky problem. For auth, MAU is only one axis and is applicable mostly for B2C with basic authentication needs.

Do you plan to add feature configuration as well (e.g. custom data residency, GDPR, SAML), or will you keep it pretty high level?

Also, are you open to a PR to add Userfront to the auth pricing?

Directionally accurate, but in the example you've chosen it's more about economics than demographics, so they'd hug and then vote to separate anyway.