Strategy 02

Voice & Tone

Plathera speaks like an owner-side project leader who has stopped tolerating fragmented truth: owner-authored, specific, sober, technically literate, and anti-vendor.

Doctrine

Owner-authored. Specific. Sober. Technically literate. Anti-vendor.

The Industrial voice is not a marketing wrapper. It is the operating discipline for every page, deck, memo, product surface, sales note, and hiring artifact. When the attributes conflict, this order wins.

What We Sound Like

We are	We are not
Exacting.	Wordy.
Industrial.	Decorative.
Evidence-led.	Claim-led.
Mechanism-first.	Benefit-first.
Owner-authored.	Vendor-authored.
Senior and calm.	Excited and loud.
Specific to capital delivery.	Generic enterprise software.
Technically literate.	Glossary-dependent.
Quietly consequential.	Launch-day theatrical.

Attribute 01

Owner-Authored

Write from inside the work, not from the vendor booth. The line should feel like it came from someone who has sat through the Friday review and knows which part of the record will be challenged Monday.

Good	Bad
Every project review starts with the same hidden tax: rebuilding what changed, who knew it, which package it touched, and whether the record can defend the decision.	Project teams are overwhelmed by data silos and need an AI-powered solution to improve collaboration.

Attribute 02

Specific

Name systems, objects, roles, times, and consequences: Aconex, ACC, Outlook, SAP, Primavera P6, RFI, permit condition, gate packet, NCR, ITP, AHJ, switchgear, commissioning package.

Good	Bad
The EOR uploaded the 90% drawing set to Aconex on Tuesday. Procurement still has the old switchgear schedule in the bid package.	Important project information lives across many systems, creating visibility challenges for teams.

Attribute 03

Sober

No exclamation marks. No hype. Describe the mechanism and let the consequence land.

The drawings are wrong. The PO has to be paused before Monday. Three review meetings do not know that yet.

Attribute 04

Technically Literate

Use the language of the work correctly without apologizing for it. The buyer knows it. The investor can infer it.

Plathera links the RFI, drawing delta, procurement hold, schedule activity, and cost exposure before the gate packet is issued.

Attribute 05

Anti-Vendor

Do not sell before describing. Do not call Plathera things the copy has not earned. The proof is the mechanism.

Worth a conversation if your team is still rebuilding project state before every executive review.

Mechanism Before Claim

Never make a value claim without naming the operating mechanism beneath it.

Weak claim	Industrial rewrite
Plathera improves execution.	Plathera relates emails, drawings, milestones, cost items, RFIs, risks, and decisions into one program model before the review starts.
Plathera gives teams visibility.	Plathera shows which evidence supports the package, which decision it affects, and what remains unlinked.
Plathera streamlines reporting.	Plathera assembles the gate packet from linked evidence instead of asking a PM to rebuild state by hand.
Plathera reduces risk.	Plathera flags when a procurement commitment depends on a drawing revision, permit condition, or unresolved RFI.

Banned / Restricted Language

Avoid	Use instead
AI-powered platform	Infrastructure for project truth
Leading platform / next-generation / game-changing	Name the mechanism, evidence, or work scene
Seamless collaboration	Shared project record
Single source of truth	Live program model / defensible project record
Unlock insights	Inspect the evidence / surface the constraint
Transform delivery	Reduce reconstruction work before decisions
Stakeholders	The EOR, procurement lead, PM, AHJ, owner, vendor, EPC lead
Mission-critical	If this slips, the line does not start
Dashboard	Register, review, packet, model, trace, control room
Copilot for EPC	EPC Assistant, only when describing assistant behavior

Surface-Specific Tone

Surface	Tone	Example
Homepage hero	Declarative, sparse, buyer-first.	Capital project data is scattered. Plathera turns it into a live program model.
Product section	Mechanistic and concrete.	Documents, schedules, packages, risks, and decisions become one live program model.
Diagram / label	Compressed, noun-led.	Variance Trace, Gate Packet, Evidence Missing.
Deck	Strategic and consequential.	The missing layer is the relationship model between the repositories.
Investor memo	Analytical, category-aware.	Three bottlenecks compound: data access, context synthesis, and admin offload.
LinkedIn / field note	Observed, specific, conversational.	Every capital team has a second job: reconstructing the project before they can manage it.
Sales email / DM	Senior, low-pressure, first-person.	Curious whether data assembly before reviews is the real bottleneck in your week.
Product UI	Short, action-oriented, familiar.	No linked evidence yet. Add drawings, correspondence, or schedule items before issuing this review.
Hiring page	Peer-authored and concrete.	You will own the path from raw project artifacts to traceable evidence records.

Page-Building Sequence

Scene → tax → mechanism → outcome.

Name the work scene, name the hidden tax, name the mechanism, then name the outcome. A page should never depend on vague transformation language.

Copy Hierarchy

Eyebrow or stamp: controlled signal label for document type, status, evidence class, phase, or current state.
H1 or H2: memory phrase, short enough for the display type to carry.
Lede: name the work scene, problem, and mechanism in one or two sentences.
Panel body: concrete explanation, one idea per paragraph.
Table or register: use when comparison, status, evidence, or substitutions need inspection.
CTA: quiet and late. The page should earn attention before asking for it.

Visual Copy Rules

Lead image sections with a clear heading, then support it with body copy.
Use amber eyebrows for evidence, current state, table headers, and active signals.
Use strong emphasis only for short, important nouns or phrases.
Keep peer cards consistent; let number, eyebrow, title, and body create hierarchy.
Name status plainly: implemented, current, forthcoming, ready for gate, evidence missing.
The design can make a line feel important, but the line still has to name the work.

Anti-Vendor Filters

Could a buyer have written it after a hard review?
Does it name the work before naming Plathera?
Does the mechanism appear before the benefit?
Would the sentence still work if the company name changed?
Is the CTA trying to create urgency the copy has not earned?
Does it claim certainty where the record only supports probability?
Does it imply the assistant replaces project leadership?

Good CTA	Bad CTA
Worth a conversation if your team is still rebuilding project state before every executive review.	Book a demo today and see the future of capital project delivery.
Send the failure mode you see most often. I read every reply.	Start your transformation journey with Plathera's AI-powered platform.

Good / Bad Copy Bank

Surface	Good	Bad
Homepage	Capital project data is scattered. Plathera turns it into a live program model.	The all-in-one AI-powered platform helping construction stakeholders unlock seamless collaboration.
Problem	The information is there. It is split across Outlook, ACC, SharePoint, schedules, spreadsheets, ERPs, and the memory of the people who were in the room.	Construction teams are drowning in disconnected tools that make it hard to collaborate efficiently.
Mechanism	Plathera ingests project artifacts, resolves them to packages, scope items, milestones, decisions, and risks, then gives the EPC team a controlled work surface.	Plathera leverages AI to provide smarter workflows and actionable insights for every stakeholder.
UI	Evidence missing. Link the drawing revision or mark the package as unverified before issuing the gate packet.	Oops! Add more data to unlock better insights.
Hiring	You will work on the evidence layer: ingestion, extraction, linking, review states, and the UI surfaces that let a project leader trust the record.	Join a fast-moving team revolutionizing the future of construction with cutting-edge artificial intelligence.

The Five-Sentence Test

Could a skeptical EPC or owner-side capital leader say it without embarrassment?
Does it name a real project object, role, system, number, or decision?
Does it explain a mechanism before a benefit?
Does it avoid generic AI, SaaS, consultant, and futurist language?
Does it make the work feel more structured, not more magical?

Sample Hero

Capital project data is scattered. Plathera turns it into a live program model. It connects the documents, schedules, packages, risks, costs, correspondence, and decisions that EPC teams already manage.

Sample Product

Plathera builds the layer beneath the review: evidence intake, project graph, agent workflows, and controlled outputs. The assistant does not guess from fragments. It reasons against the structure.

Sample Close

The result is not another place to put project information. It is a more defensible way to know what the project is.