Hey all,
Thanks again to everyone who joined us to talk through how Coda fits into the broader Superhuman Suite. Below is a summary of the questions we covered during the Q&A session following Khanh Le’s presentation. We’d love to keep the dialogue going, so feel free to add any comments below.
Community Q&A
-
@Greg_Villeneuve asked whether databases would be included in existing plans or require additional cost. Khanh confirmed that buying the bundle gets you access to databases at the corresponding tier, still subject to maker billing. Greg also asked whether upgrading to Superhuman would upgrade all workspace members or just doc makers. Khanh confirmed it’s a pay-to-pay transition, meaning only doc makers are upgraded.
-
@Tim_Richardson raised concerns about nonprofit discounts, noting that Grammarly previously discontinued its nonprofit program and that a similar move with Coda could destabilize organizations that rely on it. Khanh confirmed that existing Coda nonprofit discounts will continue as long as subscribers don’t upgrade to Superhuman, and acknowledged that discount structures are still being worked out on the Superhuman side.
-
@Greg_Villeneuve shared that at his organization, most users do fine with a base level of AI, while only a small number of power users need deeper access. He described Google Gemini’s per-user add-on model as a useful comparison and flagged that it would be hard to justify upgrading everyone to a higher-tier seat when only a few people need advanced AI.
-
@Jim_Baxley asked about model transparency and the ability to bring your own model subscription into Coda (similar to how VS Code handles it), noting that some users and organizations have strong preferences around which models they use. Evan noted that the product team works backward from the job to be done when selecting models, and the team is committed to sharing more as model choices become more visible in the product experience.
-
@Max_OBrien asked two things: first, that automations should never fail due to token exhaustion, and that there should be a way to automatically acquire more capacity without manual intervention. Second, he echoed Jim’s point about needing visibility into which model is being used and what the context window size is, noting that, for his use cases, a large context window is essential and that his clients are willing to pay for it.
-
@Kayla_Taras3 asked about the transition from table to database and what happens if an editor creates a table that grows past the row limit. Khanh confirmed editors can still create tables in docs, but converting to a database requires a maker seat. Kayla also asked about proactive notifications as a table approaches its limit, which Khanh flagged as great feedback to pass to the product team. She also raised the scenario of transferring table ownership to a maker rather than requiring the original editor to upgrade.
-
@Theo_Skye2 asked about database tier segmentation, specifically whether tiers would be based on data volume, AI capabilities, or other factors. Khanh confirmed all of those directions are under consideration, with beta usage and competitive benchmarking helping to inform where limits land.
-
@Theo_Skye2 also asked what functionality non-maker users (editors and free users) at an enterprise might get access to across the broader Superhuman Suite. Khanh noted that most editor-specific functionality will center on Coda and databases, but that AI-powered natural language experiences are expected to increasingly benefit editors across the suite over time, with more and more of those benefits extending across the suite.
This is a living conversation. Drop any follow-up thoughts below, and stay tuned for more roundtables ahead.
