Verdict
Submitted 5/31/2026, 1:03:27 PM · Completed 5/31/2026, 1:04:18 PM
Ask HN: Web editor that operate with AST?
Show original source text →
Strengths
- • Targets a high-value niche with potential for premium SaaS pricing
- • Enables precise, template-driven document assembly through AST-based editing and transformation
- • Has potential for strong unit economics with controlled customer acquisition cost
- • Can leverage existing libraries and tools for document generation and AST manipulation
- • Has a clear, real-world demand for automated, high-fidelity document generation in business environments
Weaknesses
- • High technical complexity of integrating a UI editor operating on AST nodes for multiple output formats
- • Crowded market with established solutions that might be hard to compete with
- • Risk of spreading resources too thin by targeting 'all kinds of business docs' without a clear differentiation strategy
- • User preference for visual editors over abstract syntax trees
- • Dependence on building a robust ecosystem of templates, integrations, and community contributions
Best angle
Focus on developing a WYSIWYG editor that operates on a user-definable AST and integrates with APIs like Stripe or QuickBooks to capture a loyal segment of mid-market SaaS companies, accounting firms, and legal tech teams.
Panel verdicts
Competition
nvidia/nemotron-3-nano-omni-30b-a3b-reasoning
“A niche AST‑driven UI editor could differentiate, but its durability will hinge on overcoming user preference for visual editors and competition from low‑code alternatives.”
Currently, the market offers Pandoc and Quarto for converting markup or AST‑based content into multiple formats, but they lack a dedicated visual editor that manipulates AST nodes directly. Specialized business‑doc platforms such as PandaDoc, QuoteWerks, and Proposify provide template‑driven document creation, while low‑code/no‑code tools (e.g., Retool, AppSheet, Power Apps) enable custom workflows but do not expose an AST‑centric UI. A UI editor that works natively on AST nodes would therefore fill a niche: it could let users define transformations once and generate invoices, quotes, Excel reports, PDFs, and Word files with high fidelity. However, durability is uncertain because users typically prefer WYSIWYG editors over abstract syntax trees, and low‑code platforms can be extended to mimic similar functionality, reducing switching costs. Additionally, the success of such a tool depends on building a robust ecosystem of templates, integrations, and community contributions, which may be challenging. Consequently, while the concept shows differentiation through its technical focus, the competitive landscape and user preferences temper its defensibility, leading to a moderate score.
Viability
meta/llama-4-maverick-17b-128e-instruct
“A viable approach for v1 is to focus on a limited set of document types and output formats, leveraging existing document generation and AST manipulation libraries.”
Building a UI editor that operates on AST nodes for generating various business documents (e.g., invoices, quotes, Excel reports) in multiple formats (Typst, HTML, PDF, Word, Excel) is a complex task. The complexity arises from handling different document structures, formatting requirements, and output formats. However, it's feasible for a solo or 2-person team to achieve a basic version (v1) within 4-12 weeks by focusing on a subset of the features and formats. They can leverage existing libraries and tools for document generation and AST manipulation, such as Typst, Pandoc, or other templating engines. The key challenge lies in designing a user-friendly UI that can effectively manipulate AST nodes and translating that into various output formats. A significant portion of the effort will be spent on integrating and adapting existing libraries rather than building everything from scratch. The team can prioritize the most common business documents and formats for v1, simplifying the scope. Nonetheless, achieving high-quality output across different formats, especially for complex documents like Excel reports, will be challenging within the given timeframe.
Risk
nvidia/llama-3.3-nemotron-super-49b-v1
“Technical complexity of AST-based UI editor for multi-format output, coupled with a crowded market, threatens viability within 6-12 months.”
The idea faces significant technical and market challenges. Firstly, integrating a UI editor operating on Abstract Syntax Tree (AST) nodes for multiple output formats (PDF, Word, Excel) is highly complex, requiring deep expertise in both the editor's AST manipulation and the conversion libraries (e.g., for PDF, Word, Excel compatibility). Pandoc, while versatile, may not fully address the 'nicely' aspect for all formats, especially Excel, which has unique structural requirements. Secondly, the market for document generation tools is crowded, with established solutions (e.g., DocuSign for signing and generation, Microsoft's own tools for Office formats) that might be hard to compete with, especially for a new entrant aiming to support a broad range of document types. Lastly, the specificity of targeting 'all kinds of business docs' without a clear differentiation strategy or a identified niche (e.g., legal, healthcare, e-commerce) increases the risk of spreading resources too thin.
Market
qwen/qwen3-next-80b-a3b-instruct
“The real market isn't for generating PDFs or Excel files - it's for making business document logic visually editable and version-controlled by non-developers without sacrificing precision.”
There is a clear, real-world demand for automated, high-fidelity document generation in business environments - particularly for invoices, quotes, and Excel reports - but the market is already served by established tools like DocuSign, PandaDoc, QuickBooks, and even Excel templates with Power Query. The unmet need isn't document output formats (PDF, Word, Excel) - those are solved - but rather a unified, code-aware, AST-driven editor that lets non-developers visually build and modify document templates with precision, while allowing developers to extend them programmatically. This niche exists among mid-market SaaS companies, accounting firms, and legal tech teams that need dynamic, rule-based document generation without relying on brittle Word macros or manual copy-paste. However, the audience is small: likely under 500k globally who care enough to pay for a specialized tool (not just a plugin). Most users will stick with existing workflows unless your solution offers a dramatic leap in maintainability, version control, or collaboration. Typst is promising but still niche; HTML/AST-based editing is complex and requires deep technical buy-in. The real opportunity isn't in the output formats, but in making template logic (e.g., tax rules, conditional fields, data joins) visually editable and reusable. If you can build a WYSIWYG editor that operates on a user-definable AST and integrates with APIs like Stripe or QuickBooks, you could capture a loyal segment. But the barrier to adoption is high without strong integrations and UX polish.
Monetization
mistralai/mistral-medium-3.5-128b
“AST-driven document generation unlocks precision and multi-format scalability for business workflows, justifying premium SaaS pricing.”
The idea targets a high-value niche: automated generation of business documents (invoices, quotes, reports) across multiple formats (PDF, Word, Excel, Typst, HTML). The core innovation - AST-based editing and transformation - enables precise, template-driven document assembly, which is superior to raw text or Pandoc for structured business use cases. Pricing could follow a tiered SaaS model: (1) Free tier for basic templates (e.g., 10/month), (2) Pro tier at $20 - $50/user/month for advanced AST customization, API access, and multi-format exports, (3) Enterprise at $100+/user/month for on-prem, white-labeling, and Excel/Word deep integration. Channels: Direct sales for enterprise, self-serve for SMBs, and marketplace integrations (e.g., Zapier, Shopify). Gross margins should exceed 80% due to low COGS (cloud hosting + AST processing). Unit economics are strong if customer acquisition cost (CAC) is controlled via content marketing (e.g., 'AST for business docs' tutorials) and partnerships with accounting/ERP tools. Risks: Competition from niche tools like DocRaptor or Windward, but AST flexibility is a differentiator.
Synthesized by meta/llama-3.3-70b-instruct · 16.2s