How we write honest product copy

Honest product copy at DarDev means every sentence on dardev.net, hesabi.tn, and news.dardev.net maps to software we operate—or to a roadmap item we label as planned, beta, or waitlist. We do not sell vaporware. If a feature is not in production, we say so in the same paragraph where we describe the product, not buried in a footnote or a sales-only PDF.

That discipline sits inside our Deployed Realities policy: marketing must match deployed behavior. Engineering and sales share one vocabulary for shipped, beta, and waitlist. When those labels drift, we treat the mismatch like a production regression—because overstated copy breaks trust faster than a failed deploy, and procurement teams remember the vendor who demoed features that never arrived.

Three labels we never blur

We classify capabilities in three buckets. Shipped means in production with support expectations. Beta means real code with limited scope, invite-only tenants, or known gaps documented publicly. Waitlist means directional roadmap with no general-availability promise. EscaHire recruiting automation is waitlist—we capture interest and share progress, but we do not claim it is ready for every hiring team. Hesabi TTN and TEJ workflows are shipped for Tunisia. DarDevLab labs run on clusters we maintain. Mixing those tiers is how prospects sign for modules that do not exist yet.

Shipped versus roadmap on the page

Roadmap items belong on roadmap or changelog pages marked planned, not on hero banners. When Hesabi adds a workflow, release notes on news.dardev.net describe what accountants can do today. Platform modules—Wrkspace IAM, DarDevOps pipelines, Observability—follow the same rule: we document integrations we operate, such as GitLab CI and Prometheus, not every logo that fits a partner slide. Read how we separate solutions from platform products to see which buyer motion each page serves.

• Hero copy: shipped capabilities only
• Feature grids: shipped plus beta with explicit badges
• Roadmap teasers: linked out, never implied as GA
• Sales decks: versioned and dated like release artifacts
• Pricing tables: no line items for unreleased modules

Regional honesty is product honesty

Geography is part of copy integrity. Hesabi is Tunisia-only because fiscal rules, TTN enrollment, and TEJ exports are country-specific—we do not imply Morocco or Algeria availability. DarDev Services consults across MENA on cloud migration and DevOps, but consulting reach is not product licensing. That distinction saves procurement teams from buying invoicing software that cannot file in their jurisdiction, and it keeps our Tunis engineering team focused on compliance we can defend in production.

Who reviews copy before it ships

Product managers draft. Engineers verify against production configs and feature flags. Someone who has been on-call for the stack signs off. For Hesabi, that includes an accountant-facing sanity check—if language promises a declaration we cannot file, it does not publish. For platform content, SREs confirm observability and deploy claims. This is slower than a marketing-only review, but it prevents the classic SaaS failure mode: a polished landing page and a support inbox asking where the button from the demo went.

Dogfooding as copy QA

We use our own Unified Mailer—Twenty CRM, Listmonk, Stalwart on send.dardev.net—for outreach and product lists. If Listmonk cannot do something we describe, we fix the copy or the integration before the article goes live. The same applies to crm.dardev.net and news.dardev.net: public URLs are evidence. Enterprise buyers can click through during due diligence instead of trusting a slide. See our dogfood stack article for the wiring we actually run, and our deployed-realities explainer for the company policy behind it.

When honest copy means saying no

Sometimes the most honest sentence is a referral, not a pitch. DarDev declines custom engagements when an existing product—ours or a credible market option—already solves the core workflow. Sales and engineering use the same language when recommending a Hesabi signup instead of a statement of work. Our custom-vs-product fit guide documents that posture so prospects hear one answer from the website and from discovery calls.

Copy mistakes we refuse to repeat

• Marketing waitlist products as if they were GA
• Borrowing compliance language from another country
• Hero screenshots from design mocks instead of production
• Integration grids that are logo slides without live connectors
• Roadmap bullets copied into pricing tables
• Uptime or customer-count stats we cannot substantiate

We publish corrections when customers or partners catch drift—contact@dardev.net routes to Twenty CRM and is treated as a messaging bug, not a support annoyance. Changelog entries on news.dardev.net document when copy changes because behavior shipped or because we retracted an overclaim. That audit trail is part of honest SaaS marketing: buyers should see when we fixed language, not only when we shipped code.