FAQ
Frequently asked questions
Clear answers about wallet credit, usage, subscriptions, and how Tycoon charges for work.
Is AJ really running Carrd totally solo?
By all public indicators, yes. There's no known team page, no LinkedIn connections to a Carrd team, and AJ has repeatedly described Carrd as a solo operation in the limited public communication he does. There may be contractors for specific tasks at times, but the core operation — engineering, product, support, operations — is one person. This is especially notable because Carrd's scale (millions of sites) would normally imply a team of 10+ in any traditional SaaS org.
Why does AJ stay so quiet publicly?
Personal preference, based on what he's said in rare interviews. Public visibility creates expectations, demand for engagement, and opportunity cost. AJ appears to have decided early that the marginal dollar from public hype was not worth the marginal hour it consumed. The product compounds whether he posts or not; his time compounds only if he spends it building. This is a deliberate choice that happens to be anti-pattern relative to the 'build in public' orthodoxy but works for AJ specifically.
What would AJ's playbook look like with AI tools in 2026?
Hard to say because AJ hasn't said much publicly. The obvious compressions are customer support (AI CSM role), content marketing (which AJ basically doesn't do), and routine engineering maintenance (AI CTO role as a collaborator). The non-obvious question is whether AI changes the product — Carrd's simplicity is deliberate, and adding 'AI features' for their own sake would break the scope discipline that is Carrd's actual edge. The most likely answer is AJ uses AI tools quietly for his own productivity and doesn't advertise it, same pattern as everything else.
Is the Carrd model replicable?
Partially. The transferable elements: pick a narrow scope, charge modestly, ship quality, stay focused, don't raise money. The less transferable elements: AJ's frontend craft background, his temperament for quiet operation, and his willingness to run in maintenance mode for years. The model works for founders who are good at the craft, have patience, and don't need external validation. It's not the right shape for founders who want fast growth, public recognition, or an eventual exit.
What happens to Carrd if AJ stops working on it?
This is the classic concentrated-risk question for solo SaaS, and Carrd has no public succession plan. Scenarios: AJ could sell the business (a $1M+ ARR solo SaaS with high margins is a clean acquisition target), he could hire a small team to take over, he could let it run in fully automated maintenance mode, or he could sunset it. For customers, it's a real consideration — which is why some users hedge by not using Carrd for mission-critical sites. This is the tradeoff: Carrd is cheap and good because it's one person; one person means no redundancy. Users trade the redundancy for the price and quality.