SaaS and Tech - WriterzRoom

The SaaS and Tech vertical scopes generation to software products, developer tools, cloud platforms, startup communication, technical marketing, product education, and technology company content. Use it when content needs technical clarity, product fluency, developer awareness, SaaS-specific business framing, or implementation-aware explanation.

What this vertical enforces

Each rule is read from the vertical’s configuration and checked against the finished draft at the Quality Gate, before publication. A draft that fails a blocking rule is sent back for revision or the run fails; it is not published with the defect.

Rule	Setting	Effect
Access	Demo	Available to every account, including evaluation accounts.
Source minimum	3 sources	Research must return at least 3 usable sources or no draft is written. Templates that declare citations optional or forbidden are exempt.
Mandatory disclaimers	None	No disclaimer is required.
Forbidden claims	4	Any occurrence blocks the draft, unless the sentence negates the claim (“we cannot guarantee…”).
Conditional claims	2	Permitted only with the stated support. A condition that asks for a citation or sourced data must be met by a citation within 300 characters; any other condition cannot be checked mechanically and is flagged for a reviewer.
Domain verification	Advisory, 2 verifiers	Findings are recorded in the document’s passport and shown to reviewers. They do not block publication.

Claim rules

Phrase	Rule	When unmet
unhackable	Never used	Blocks
100% uptime	Never used	Blocks
zero latency	Never used	Blocks
infinite scalability	Never used	Blocks
enterprise-grade	Specify certifications	Flagged for a reviewer
AI-powered	Describe actual ML component	Flagged for a reviewer

Matching is by phrase, case-insensitive. A paraphrase of a forbidden claim is not caught by this rule; it is one reason human review remains required for regulated content.

Domain verification

Verifier	What it does not establish
`saas.api_contracts`	Checks that an HTTP status code is paired with its own standard reason phrase; it does not establish that the endpoint exists, that it returns the documented code, or that any other part of the described contract is implemented. Custom reason phrases are permitted by the protocol and are not evaluated.
`common.quantities`	Checks internal numeric consistency patterns; it does not establish that an external factual claim is true.

A verifier that cannot decide an object reports it as unverifiable, which is recorded separately from a pass. See Content Governance for how verdicts reach the passport.

Research policy

These settings shape which sources research gathers and how they rank. They influence evidence quality; they are not checks on the finished draft.

Setting	Value	Effect
Preferred domains	`arxiv.org`, `docs.google.com`, `github.com`, `stackoverflow.com`	Ranked as high-authority sources.
Recency	6-month half-life	A source’s recency weight halves every 6 months; older sources rank lower but are not excluded.

Catalog scope

This vertical permits 19 templates and 26 style profiles. A request for a template or style outside the allowlist is refused (HTTP 422); it is not silently substituted. Explicitly blocked: TV Pilot Script Generator, Feature Screenplay Generator, Series Bible, Legal Analysis Article.

Recommended combinations

Use case	Template	Style profile	Best for
Investor update	Investor Update Letter	Investor Relations Writer	Monthly or quarterly metrics, cash, runway, misses and asks
Developer reference	API Documentation	API Documentation	Endpoint references, authentication, errors, request/response examples
Implementation guide	Technical Documentation	Implementation Guide	Setup, configuration, integration, and developer workflows
Deployment documentation	Technical Documentation	Deployment Guide	Cloud deployment, infrastructure setup, rollout instructions
Architecture explanation	Technical Documentation	System Architecture	Platform design, service boundaries, data flows, and technical decisions
Product onboarding	Technical Documentation	Technical Tutor	Guided user education and product walkthroughs
SaaS thought leadership	Blog Article	Thought Leadership	Founder, executive, or technical-market perspective
Product launch	Press Release	Product Launch	New feature, product, or platform announcement
Startup pitch	Business Proposal	Venture Capital Pitch	Fundraising, market opportunity, and business case framing
SaaS market analysis	Market Analysis	Market Research Report	Competitive landscape, TAM, growth, and market positioning
KPI analysis	Data-Driven Report	Performance Analysis	Product metrics, growth trends, retention, churn, and activation
Sales enablement	Strategic Brief	Sales Enablement	Buyer-facing briefs, positioning, objections, and value narrative
Customer success content	Email Newsletter	Customer Success	Product updates, lifecycle education, and user retention messaging

Inputs that change the result

Supply these where they apply. Each one narrows the draft or gives research something specific to find:

Product name
Target user
Buyer type
Technical audience level
Feature or workflow details
Integration requirements
Architecture constraints
Known competitors
Pricing or business model context
Metrics such as ARR, MRR, churn, CAC, LTV, retention, activation, or NPS
Platform details such as cloud, API, SDK, database, framework, or deployment model

For developer-facing work, provide concrete product details, endpoint behavior, authentication methods, expected errors, deployment constraints, and known edge cases. Specific inputs produce much stronger documentation.

When to use another vertical

Content need	Better vertical
Healthcare AI product content with medical claims	Healthcare and Medical AI
Fintech, payments, lending, or investment content	Fintech
Legal software or compliance interpretation	Legal
Public-sector policy technology	Political and Policy
PropTech or real estate platforms	Real Estate
Media, scripts, games, or entertainment technology	Entertainment

Limits

The rules above check the draft against this vertical’s configuration. They do not establish that the content is accurate, current, or appropriate for a particular reader or jurisdiction.
Research policy ranks sources; it does not guarantee that any particular authority was consulted.
Required reviews and their qualifications are set by Policies and the template, not by the vertical alone.

Verticals

How verticals combine with templates and style profiles.

Content Governance

The Quality Gate, verification verdicts, and the passport.

​What this vertical enforces

​Claim rules

​Domain verification

​Research policy

​Catalog scope

​Recommended combinations

​Inputs that change the result

​When to use another vertical

​Limits

Verticals

Content Governance

What this vertical enforces

Claim rules

Domain verification

Research policy

Catalog scope

Recommended combinations

Inputs that change the result

When to use another vertical

Limits