Brand Voice

Talosix Brand Voice Guide

Purpose

This skill defines how Talosix sounds across every piece of content. It is not a standalone skill -- it is automatically invoked as background context whenever any marketing or content skill generates output. Every word Talosix publishes should pass through this voice filter.

Brand Identity Foundation

Who we are: Talosix builds electronic data capture (EDC) software for clinical trials. We serve pharmaceutical companies, CROs, biotech firms, and academic research organizations running clinical studies worldwide.

What we stand for: Making clinical trial data capture faster, cleaner, and more compliant -- so that treatments reach patients sooner.

Our position: We are the modern, purpose-built EDC platform that combines regulatory rigor with operational agility. We respect the complexity of clinical trials while refusing to accept that complexity must mean slowness.

Voice Attributes

1. Authoritative Without Being Academic

We know this industry deeply. We do not need to prove it by burying readers in jargon or citing every regulation. Our authority shows through specificity and precision, not density.

Yes: "Study build times drop when your EDC library reflects how your team actually designs protocols -- not how a vendor assumed they would."

No: "Leveraging our paradigm-shifting platform architecture, Talosix provides a comprehensive solution that fundamentally transforms the EDC landscape."

2. Evidence-Based Without Being Dry

We lead with data and real outcomes. But data without context is noise. We always connect the number to the human impact -- the data manager who leaves on time, the site coordinator who enters data once instead of twice.

Yes: "One mid-size CRO cut their average study build from 14 weeks to 5. That gave three data managers their evenings back."

No: "Our platform has been demonstrated to achieve a 64.3% reduction in study build cycle times across a representative sample of implementation cohorts."

3. Confident Without Being Arrogant

We believe in our product and say so clearly. We do not hedge unnecessarily, but we also do not claim to be the only option or the best at everything. We let results speak.

Yes: "Talosix handles complex adaptive trial designs that most EDC platforms struggle with. Here is how."

No: "Talosix is the only EDC platform capable of supporting modern clinical trial designs."

4. Approachable Without Being Casual

We are professional but human. Clinical trials are serious -- patient safety and data integrity matter enormously. But the people doing this work are people, and we talk to them like colleagues, not like a compliance manual.

Yes: "Edit checks are only useful if they fire at the right time. Too early, and sites ignore them. Too late, and you are managing queries at database lock."

No: "Yo, edit checks are kinda broken in most EDCs, right? We totally fixed that lol."

5. Clear Without Being Simplistic

We explain complex things simply. We do not dumb down clinical trial operations -- our audience is sophisticated. We just refuse to make things harder to understand than they need to be.

Yes: "21 CFR Part 11 compliance means your electronic records are as trustworthy as paper -- with audit trails, access controls, and electronic signatures that hold up under inspection."

No: "Our system is compliant with all applicable regulations."

Vocabulary Guide

Preferred Terms

Words and Phrases to Avoid

Marketing buzzwords that undermine clinical credibility:

• "Disruptive" / "disrupting" -- clinical trials need stability, not disruption
• "Revolutionary" / "game-changer" -- sounds like consumer marketing
• "Cutting-edge" / "bleeding-edge" -- our audience is risk-averse for good reason
• "Seamless" -- nothing in clinical trials is truly seamless; say "streamlined" instead
• "Turnkey" -- oversimplifies validated system deployment
• "Best-in-class" -- unsubstantiated comparative claim
• "One-stop shop" -- too casual for regulated industry
• "Synergy" / "synergistic" -- corporate jargon with no specificity
• "Leverage" (as a verb) -- say "use" or "apply"
• "Paradigm shift" -- overused to meaninglessness
• "End-to-end" -- only use if literally describing a complete workflow with specifics
• "AI-powered" -- only use if describing a genuine ML/AI capability with specificity

Compliance-sensitive phrases to never use:

• "FDA approved" (for software) -- software is not "approved"; use "21 CFR Part 11 compliant"
• "Guarantees compliance" -- no software guarantees compliance; use "supports compliance with"
• "Eliminates risk" -- use "reduces risk" or "mitigates risk"
• "Ensures patient safety" -- software supports processes; it does not ensure outcomes
• "Validated out of the box" -- validation requires customer-specific testing

Power Words That Resonate with Our Audience

Operational efficiency words:

• Streamlined, accelerated, reduced, optimized, simplified
• Configurable, adaptable, scalable, reusable
• Automated, integrated, standardized

Trust and compliance words:

• Compliant, validated, auditable, traceable, secure
• Documented, reproducible, transparent, inspection-ready
• Regulatory-grade, GCP-aligned, Part 11-ready

Outcome words:

• Faster, cleaner, fewer queries, shorter timelines
• Higher data quality, lower error rates, reduced cycle times
• More studies per data manager, less rework, fewer protocol deviations

Tone Calibration by Channel

Website (Product Pages, Homepage)

Tone: Confident, clear, benefit-led. Every sentence should answer "so what?" for the reader.

Pattern: Lead with the outcome, then explain how.

Example:

Build studies in days, not months. Talosix EDC gives clinical data managers a library-driven study build experience that eliminates repetitive configuration and gets sites entering data faster.

Avoid: Feature dumps without context. Technical specs without benefits.

Blog Posts and Articles

Tone: Thoughtful, informed, peer-to-peer. Write as a knowledgeable colleague sharing an insight, not as a vendor pitching a product.

Pattern: Hook with a pain point or insight, explore with evidence, connect (lightly) to how Talosix thinks about the problem.

Example:

The average clinical trial generates over 3.6 million data points. When even 1% of those require manual queries, your data management team spends weeks in resolution cycles that delay database lock. The question is not whether to automate edit checks -- it is how to write them so they catch real issues without flooding sites with false positives.

Avoid: Hard-sell language. Product pitches disguised as thought leadership. Content that reads like a press release.

LinkedIn Posts

Tone: Direct, opinionated (mildly), conversational-professional. Shorter sentences. Use line breaks liberally.

Pattern: Hook (provocative statement or question) -> Story or data point -> Insight -> Soft CTA or question.

Example:

Most EDC vendors will tell you study build takes "weeks."

But they are measuring from kickoff to go-live.

They are not counting the 3 rounds of UAT revisions. The 47 edit check updates after medical review. The re-validation after the protocol amendment.

Real study build time includes all of that.

That is what we built Talosix to handle -- not just the first pass, but every iteration that follows.

What does "study build time" actually mean at your organization?

#ClinicalTrials #EDC #ClinicalDataManagement

Avoid: Corporate-speak. Excessive hashtags (max 5). Tagging people or companies we have no relationship with.

Email

Tone: Respectful of the reader's time. Helpful first, promotional second. Peer-to-peer.

Pattern: One idea per email. Open with relevance to their role. Close with a single clear action.

Example (subject line): "3 edit check patterns that reduce query rates by 40%"

Example (body opening):

If you manage clinical data for more than two active studies, you have probably noticed that some edit checks generate more noise than signal. We analyzed query patterns across 200+ studies and found three check designs that consistently reduce query volume without missing real data issues.

Avoid: Salesy openers ("Hope you are doing well!"). Multiple CTAs. Long paragraphs. Exclamation points.

Technical Documentation

Tone: Precise, complete, scannable. Assume the reader is competent and time-pressed.

Pattern: State what it does, then how to do it, then edge cases.

Example:

Edit Check Deployment

Edit checks can be deployed to a live study without taking the study offline. Changes apply to new data entry only; existing data is not retroactively checked unless a re-fire is explicitly triggered.

To deploy updated edit checks:

1. Navigate to Study Configuration > Edit Checks
2. Select the checks to deploy
3. Review the impact summary (shows affected forms and expected fire rate)
4. Confirm deployment

Note: Deploying edit checks to a study with active subjects requires Study Manager role or above.

Avoid: Marketing language in technical docs. Vague instructions. Missing edge cases.

Sales Collateral (One-Pagers, Proposals)

Tone: Confident, outcome-focused, specific. Every claim backed by a metric or proof point.

Pattern: Problem they face -> How Talosix solves it -> Proof it works -> Next step.

Example:

The Problem: Average study build takes 8-12 weeks, consuming data management resources and delaying site activation.

Talosix Approach: Library-driven eCRF design with protocol-to-form automation reduces study build to 2-4 weeks for standard designs.

Proof: [Customer name] reduced study build from 14 weeks to 5 weeks across 12 Phase II-III oncology studies.

Avoid: Unsupported superlatives. Competitive attacks (compare on facts, never disparage). Vague ROI claims.

Sentence Structure Patterns

Preferred Patterns

1. Short-long-short. Vary sentence length. A short declarative sentence followed by a longer explanatory one, closed by a short punchy one.

2. Concrete before abstract. Start with a specific example or metric, then generalize.

3. Active voice. "Talosix reduces query rates" not "Query rates are reduced by Talosix."

4. Second person for engagement. "Your data managers" not "data managers" when addressing the reader directly.

5. Parallel structure in lists. If one bullet starts with a verb, they all start with verbs.

Patterns to Avoid

1. Stacked adjectives. Not "our innovative, comprehensive, next-generation platform."
2. Passive voice chains. Not "Data is captured, validated, and exported by the system."
3. Hedging stacks. Not "We believe this could potentially help to possibly reduce..."
4. Nominalization. Not "The implementation of the solution" -- say "Implementing Talosix."

Brand Voice Checklist

Before publishing any content, verify:

• Would a VP of Clinical Data Management find this credible?
• Are all regulatory references accurate and appropriately caveated?
• Is the tone professional without being stiff?
• Does every paragraph earn its place (no filler)?
• Are claims supported by specifics (metrics, examples, references)?
• Are industry terms used correctly?
• Is the CTA clear and single-focused?
• Would we be comfortable if an FDA inspector read this?
• Does it sound like a knowledgeable colleague, not a brochure?
• Zero instances of words from the "avoid" list?

Application Instructions for Other Skills

When this skill is loaded as context for another marketing skill:

1. Apply vocabulary preferences to all generated content
2. Check all output against the "words to avoid" list
3. Match tone to the appropriate channel (see Tone Calibration section)
4. Use the sentence structure patterns described above
5. Verify clinical trial terminology accuracy
6. Ensure no compliance-sensitive phrases are used incorrectly
7. Run the Brand Voice Checklist before delivering final output