Service FAQs
Added pricing, timeline, deliverables, and support guidance as ranges or scope-dependent expectations instead of fixed promises.
Proof system
Content claims must be traceable, labeled, or safely scoped.
These guidelines keep RelenshTech content credible. Metrics, testimonials, outcomes, and scale claims should only be published when the proof source is clear.
Approved Proof Types
Verified client testimonial
Anonymized project example
Case study
Screenshot
Metric with source
Public link
Repository link
Documentation link
Changelog
Proof Labels
Verified client
Anonymized project
Internal product
Public plugin
Metric verified by analytics
Admin and Content Guidelines
Do not publish precise numbers for experience, projects, clients, team size, downloads, uptime, latency, revenue, SEO growth, or conversion lift unless the source is attached.
Use "target," "goal," "selected project outcomes," or "defined per agreement" when a number depends on scope, analytics access, or contract terms.
Testimonials must be labeled as verified client feedback or anonymized project feedback. If the client cannot be named, remove role, company, and metric claims that imply verification.
Case studies must state permission status, proof artifact, and whether metrics are public, anonymized, or unavailable.
Plugin download, install, and rating claims must be hidden or marked unavailable unless verified from RelenshTech analytics or a public marketplace source.
Team claims should describe the operating model, not inflated headcount. Use "focused core team and specialist partner network" unless payroll data is approved for publication.
Unsupported-Claims Cleanup Log
Plugin marketplace
Plugin metrics show verified labels only when RelenshTech has a reliable source; public download counts remain hidden when unavailable.
Case studies and testimonials
Project outcomes are labeled as anonymized examples unless client identity and metrics are approved for public use.
Team and company claims
Company positioning uses founded January 2024, remote-first studio, focused core team, and specialist partner network.
Footer and support claims
Availability, response windows, and support coverage are described as defined per agreement.
Odoo implementation page
Replaced "Certified Odoo Partner," "Top Tier Implementation Experts," "98% retention," "Certified Experts," and ROI-style wording with scoped implementation support, agreement-based support, and cost-aware planning.
Contact page social links
Removed hardcoded LinkedIn, Twitter, and GitHub profile links from the contact page until account ownership is verified.
Admin SEO dashboard placeholders
Replaced fake traffic, click, CTR, trend, country, and page-performance values with "Connect data" and "Source required" placeholders.
Legacy home components
Replaced unsupported satisfaction, SOC2, 2x speed, response-window, data-breach, and support-cost-reduction claims with scoped, agreement-based, or source-neutral wording.