The documented set, as listed on the working canvas: business cards, letterhead, notepad, merch, social media banners, social media profile pictures, social media post templates, posters and advertisement. The client guide additionally shows: webinar and event graphics, conference/stage banners, a Coming Soon web page, hiring post templates, and an email/contact block.

Worked examples in hand:

• Business card — light gradient front with name, role, contact set small; reverse is a full-bleed blue isometric slab landscape with the wordmark.
• Letterhead — horizontal lockup top-left, address block top-right, generous margin, a gradient element anchoring one corner.
• Hiring post — "Now Hiring / Founding Engineers" with location, the YC "BACKED BY" block, and the tagline; four ground variants (pale green, cream, pale blue, dark navy).
• Webinar graphic — title left, W-masked portrait right, Roboto Mono pill CTA, date and time; on cream, green or black grounds.

DO carry the system through: chosen ground, Dark Blue or white text, gradient or slab imagery, W-masked photography. DON'T introduce off-system layouts, colours or type on any surface.

Banner lines seen in the delivered set: "Take your supply chain for granted." and "The only way forward."

Carousel and wide frames also exist at 3497 × 2000 and 4261 × 2000 — these are multi-panel layouts drawn side by side on one canvas, not export sizes. Cut them into 2000 × 2000 panels before posting.

DON'T put a full lockup in a profile picture — use the Icon.

Waybill is not a carrier. Do not place the mark on trucks, shipping containers, aircraft, parcels or boxes in a way that implies Waybill owns the vehicle or ships the freight itself.

⚠ Note what this rule does NOT say. Logistics imagery — containers, trucks, conveyors, aircraft — is core brand photography and is used throughout the delivered guide. The rule is about the LOGO on freight, not about the subject matter.

The one deliberate exception is a real waybill/label context reading "integrated with Waybill" or "tracked by Waybill" — that signals the system, not the freight.

DO keep the mark to Waybill's own surfaces, and use logistics imagery freely. DON'T brand a vehicle or a parcel as though Waybill operates it.

Make procurement effortless for the people building hard things. An engineer asks for a part and it arrives — sourced, negotiated, bought, moved across borders, and put on the shelf — without anyone chasing it. The promise Waybill states in its own words: "We get you what you need by when you need it, period."

DO frame the win as hours and hand-offs given back. DON'T describe Waybill as paperwork software; it is the thing that makes the chasing disappear.

⛔ REFRAMED 2026-08-13 (Mudit). LEAD WITH PROCUREMENT, NOT WITH THE OPERATING SYSTEM. This section previously opened "Waybill is an operating system for supply chains", which describes where the company is going rather than what it sells today. Writing to that made every line overstate the product.

Today, Waybill solves PROCUREMENT for deep-tech and hardware companies. Two halves make it work: agentic sourcing (agents find every supplier globally within your constraints — price, lead time, MOQ — and negotiate on your behalf) and owned fulfilment (in-country partners in Hong Kong, China, SEA, India and the US act as fulfilment channels, so goods restricted by jurisdiction still reach the buyer). Waybill owns that chain end to end: sourcing, negotiation, fulfilment.

The shape to aim for: "One entry point. One chain of custody. An Amazon-like experience for industrial procurement."

DO lead with procurement, and with the end-to-end ownership that differentiates it. DO treat the supply-chain operating system as the direction of travel — see Roadmap. It is a true statement about ambition and a false one about what a customer can buy today. DON'T open a description of Waybill with "operating system for supply chains". DON'T position Waybill as an India customs or import product. India is one fulfilment corridor of five, not the market.

• Agentic sourcing. Agents search globally within the buyer's constraints and negotiate on their behalf.
• Owned fulfilment. In-country partners (Hong Kong, China, SEA, India, US) carry the goods, including where jurisdiction restricts them. Modelled on Fulfilled-by-Amazon: Waybill keeps the last mile for consistency.
• The platform around it. Component-level intelligence (end-of-life alerts, alternate sources), and a lightweight ERP where inventory builds itself as agents fulfil orders — in Waybill's words, "engineers hate paperwork and SAP is absurd for this."

⚠ THE LAST BULLET IS FURTHEST FROM SHIPPING. Sourcing and fulfilment are what Waybill does today; the ERP, agentic accounting and the wider operating system are the direction of travel. Describe them as where this is going, never as what a customer gets now.

DO be specific about the mechanics; specificity is the proof. DON'T invent capabilities, and do not claim customs-broker filing. DON'T present the platform layer as available. If a sentence needs it to be true today, rewrite the sentence.

Exclusively aerospace, defence, robotics and deep-tech right now — high-frequency, high-criticality purchasing. As Waybill puts it: "R&D cycles never end, and the pain pinches hardest there."

DON'T broaden the stated focus to "manufacturing" or "logistics" generally.

Engineers and founders at hardware and deep-tech companies, who lose days to procurement instead of building. The operators and administrators who sign off — approvals, budget, compliance. And investors (YC S26), for whom the category and the owned-fulfilment moat are the story.

The brand's own line for the dual audience: "The only thing both engineers and administration love."

DO shift emphasis by reader: time-back for engineers, control and visibility for administration. DON'T write one flat message for "customers".

Waybill describes today in specifics, and the specifics are the argument: "An engineer messages 15–20 suppliers on Alibaba, ten reply, four days of back-and-forth follow, seven reject you on MOQ, and you place redundant orders with the remaining three hoping one ships. Then you separately coordinate freight, customs brokers, and last-mile. The box passes through five or six hands, and information dilutes at every handoff."

DO use these numbers when the audience needs the problem made real. DON'T round or embellish them — they are the client's own count.

In production, resilience takes over: "you need failbacks for a thousand components, plus provenance and auditability that no random trader can give you when the FDA or a defense auditor comes asking." This is why the focus is high-criticality rather than general manufacturing.

⭐ THIS SEGMENT EXISTS SO THE POSITIONING CAN STAY HONEST. Added 2026-08-13 (Mudit). Waybill today solves procurement for deep-tech and hardware companies. The larger ambition — and it is a real one, in Rishi's own words — is more products on top of that, arriving at an operating system for supply chains.

Both statements are true. They are true at different times, and the brand file previously collapsed them into one sentence that described the destination as though it were the current product.

• Now: agentic sourcing and owned fulfilment. This is what a customer buys.
• Next: component-level intelligence, a lightweight ERP where inventory builds itself as agents fulfil orders, agentic accounting for cross-border compliance.
• Eventually: one operating layer where every moving part of the chain works together.

DO use the future framing when it is genuinely useful — investors, hiring, a vision slide — and label it as direction. DON'T describe the destination in the present tense. "Waybill is an operating system for supply chains" is a sentence about the future written as though it were true today, and it is the specific error this segment was added to prevent.

Calm, exact, quietly powerful. Infrastructure, not hype. Confidence comes from what the system does, never from volume.

⚠ A LOUDER PERSONALITY EXISTS AND IS DELIBERATELY NOT SERVED HERE. Decided 2026-08-13 (Mudit): the Client Guide is the deliverable and the deliverable is brand truth — material outside it does not become brand truth, even when it is an explicit client statement.

The Presentations deck's "Our north star" slide states, verbatim: "Bold, not soft. Simple, not simplistic. Opinionated, not agreeable. Confident, not corporate. Human, not AI-first." The same deck says "not soft but polarising."

That is a different register from the line above, on the axis that matters most to a writer: how loud to be. It is recorded rather than adopted for two reasons. It is dated 03-07-2026, three weeks before the guide, and it sits in a deck whose product story — customs brokerage — the company has since replaced. And the guide, which is the deliverable, never states a personality at all; the line above is read off the delivered work.

★ Be honest about what this line therefore is: an inference from how the delivered guide behaves, not something Waybill wrote. Its status is inferred for that reason.

Which register, by surface (decided 2026-08-13, Mudit)

Both registers are real, and they are split by surface, not blended. Pick from where the words will appear, before writing a line.

BOLD - campaign lines, social posts, banners, advertising. Opinionated, a stated point of view, willing to be disagreed with. This is where "Procurement runs on email. That's the whole problem with it in four words." belongs.

CALM - website, hiring posts, decks, email, product UI, documentation, error and system copy. Exact, quietly powerful, infrastructure not hype; confidence from what the system does.

⚠ The website is CALM, and that is the counter-intuitive one - a marketing surface written in the quiet register. Deliberate: the site is where a buyer evaluates, and credibility there comes from precision, not volume.

★ Bold is not loud. In the bold register the craft rules still hold - no hype words, no exclamation marks, nothing from the avoid list. Bold means taking a position, not raising the voice. If Waybill says "no, we

meant bold", this segment changes — it is question 9 on the open list, and the strongest single reason to ask.

• Plain and declarative. Short sentences that land. "Procurement runs on email. That's the whole problem with it in four words."
• Precise. Exact nouns — GMV, MOQ, lead time, end-of-life, chain of custody.
• Quietly powerful. Confidence carried by what the system does. Understatement over hype.
• Warm about the human cost. The copy keeps naming the chasing, the hand-offs, the paperwork — the brand is on the reader's side.

DO lead with the concrete — the part, the order, the hand-off removed. DON'T use hype ("revolutionary", "cutting-edge", "game-changing") or breathless AI marketing. SHOW on: "Fewer hand-offs. Faster builds. One system doing the work." / off: "Waybill revolutionises logistics with cutting-edge AI!"

Formality 3 of 5 — professional and spare. Contractions fine. One idea per sentence. Fragments are used deliberately in campaign lines and that is on-brand.

DON'T open with corporate throat-clearing ("We are pleased to announce").

Waybill is intelligent infrastructure. "Agentic" and "agents" are used as precise technical descriptions of how the product works — that is correct and on-brand. What is off-brand is "AI" as a selling point in itself.

DO say what the agents do ("find every supplier within your constraints and negotiate on your behalf"). DON'T brand it "AI-powered".

• Engineers / founders: time back, fewer hand-offs, no chasing.
• Administration / approvers: control, visibility, chain of custody — "with you still in command."
• Investors: category, owned fulfilment, the compounding supplier network.

DON'T flatten these into one voice.

Canonical tagline: "Take your supply chain for granted." It appears in the signed-off client guide and on the delivered banners.

⚠ A second line, "Put your supply chain on Autopilot.", is set as finished artwork on the working canvas and annotated there as "also, new tagline". It is recorded as a proposed successor, pending client confirmation — do NOT present it as the tagline until Waybill confirms.

Everything else is a campaign or descriptor line (see messaging), never the tagline.

DO use "Take your supply chain for granted" as the canonical line. DON'T alter its wording, or promote a descriptor to tagline status.