Docs / Building in public

We build in public. This is the engine that does it.

A one-line brief about what shipped goes in. A log, a LinkedIn post, an X thread and a visual come out — drawn from the real work, written in one voice.

Brief in

› shipped the Pye rewards-selling widget — pye.fi/widget

The engine

Marketing engine

Gather real evidence

Draft, log first

Voice-check

Artifacts out

Lognarrative

LinkedInderived

Thread5 posts

Visualscreenshot

Why in public

Showing the work is the work.

Ship, then say so
Nothing is announced before it exists. Every post is drawn from shipped work and real deliverables — not intentions.
One narrative, every channel
The log is written first. The LinkedIn post and the thread are derived from it, so the story holds wherever you read it.
Drafts, never autopilot
The engine writes. A person publishes. Nothing posts itself, and nothing leaves without a read.

The engine

Six stages, one pass.

A single run takes a one-line brief about what shipped and returns a full set of channel-ready drafts.

01ShipSomething real lands — a feature, a deliverable, a decision.
02GatherPull the actual evidence: commits, deliverables, the work itself.
03DraftWrite the log first, then derive the LinkedIn post and thread.
04Voice-checkHold every draft against the studio voice before it survives.
05ReviewDrafts surface for a read — and, on engagements, a vote.
06PublishA person copies it out. The studio publishes; nothing auto-posts.

What comes out

The output, as it actually appears.

A true run: the Pye rewards-selling widget ship. The same story, shaped for each channel — with a visual of the product alongside it.

Daniel Urquhart

Designer who ships software · 1d

Shipped the Pye rewards selling widget this week. Live at pye.fi/widget. The widget is the consumer-facing primitive on top of the Pye Exchange. A user with staked SOL picks a lock window of up to nine months…

Visual assetpye.fi/widget

Sell your future rewards

Lock window9 months

You receive todaySOL upfront

Protocol fee0.50%

Confirm

23 validators · non-custodial · stake stays delegated

visual = product screenshot · representation, live capture to follow

Daniel Urquhart @DanielUrq · 1/

Shipped the Pye rewards selling widget this week — pye.fi/widget. A consumer-facing primitive that turns future staking rewards into SOL paid upfront, without the user ever unstaking.

197 / 280

Mechanism: lock your stake for a window up to nine months, receive a Principal Token as a 1:1 receipt, Pye sells the rewards stream on its orderbook, you get SOL today.

236 / 280

At maturity the receipt redeems for full SOL. Before maturity, the receipt itself is tradable on the orderbook. Flat 0.50% fee on proceeds, no hidden costs.

181 / 280

Different artifacts, different rooms

One ship, written for three rooms.

Peers & builders
X threads · essays · the log
They come for the craft and the mechanism. The currency is ideas, and the payoff is reputation — inbound by reputation.
Prospective partners
LinkedIn · case studies · docs
They come to judge whether you ship and think clearly. The currency is credibility and taste, and the payoff is an engagement.
The record & future-you
the log
The honest account of what shipped and why. It is both the archive and the source every other channel is derived from.

One voice

Every draft is held to the same brief.

Each channel is checked against the same voice before it ships — so the studio sounds like itself, not like a feed.

Sounds like

quietpluralconsideredpartner, not client

Never

passionatecutting-edgeinnovativeemoji!

Review & publish

On engagements, the room gets a vote.

For partner work, each draft surfaces inside the engagement so the team can weigh in before anything is published. Advisory only — the owner still decides.

urquhart.design/e/pye/marketing/widget

Draft preview

linkedin · rewards-selling-widget

Shipped the Pye rewards selling widget this week. Live at pye.fi/widget. The widget is the consumer-facing primitive on top of the Pye Exchange…

Team vote · advisory

Yes, ship itNot yet

example tally · owner decides

A quiet meta-note

This page came through the same engine.

Documentation, marketing, deliverables — they run on one pipeline, drawn from the same source, written in the same voice.

How the portal works →Message on X →LinkedIn →

Urquhart Design

Docs / Building in public

We build in public. This is the engine that does it.

A one-line brief about what shipped goes in. A log, a LinkedIn post, an X thread and a visual come out — drawn from the real work, written in one voice.

Brief in

› shipped the Pye rewards-selling widget — pye.fi/widget

The engine

Marketing engine

Gather real evidence

Draft, log first

Voice-check

Artifacts out

Lognarrative

LinkedInderived

Thread5 posts

Visualscreenshot

Why in public

Showing the work is the work.

Ship, then say so
Nothing is announced before it exists. Every post is drawn from shipped work and real deliverables — not intentions.
One narrative, every channel
The log is written first. The LinkedIn post and the thread are derived from it, so the story holds wherever you read it.
Drafts, never autopilot
The engine writes. A person publishes. Nothing posts itself, and nothing leaves without a read.

The engine

Six stages, one pass.

A single run takes a one-line brief about what shipped and returns a full set of channel-ready drafts.

01ShipSomething real lands — a feature, a deliverable, a decision.
02GatherPull the actual evidence: commits, deliverables, the work itself.
03DraftWrite the log first, then derive the LinkedIn post and thread.
04Voice-checkHold every draft against the studio voice before it survives.
05ReviewDrafts surface for a read — and, on engagements, a vote.
06PublishA person copies it out. The studio publishes; nothing auto-posts.

What comes out

The output, as it actually appears.

A true run: the Pye rewards-selling widget ship. The same story, shaped for each channel — with a visual of the product alongside it.

Daniel Urquhart

Designer who ships software · 1d

Visual assetpye.fi/widget

Sell your future rewards

Lock window9 months

You receive todaySOL upfront

Protocol fee0.50%

Confirm

23 validators · non-custodial · stake stays delegated

visual = product screenshot · representation, live capture to follow

Daniel Urquhart @DanielUrq · 1/

Shipped the Pye rewards selling widget this week — pye.fi/widget. A consumer-facing primitive that turns future staking rewards into SOL paid upfront, without the user ever unstaking.

197 / 280

Mechanism: lock your stake for a window up to nine months, receive a Principal Token as a 1:1 receipt, Pye sells the rewards stream on its orderbook, you get SOL today.

236 / 280

At maturity the receipt redeems for full SOL. Before maturity, the receipt itself is tradable on the orderbook. Flat 0.50% fee on proceeds, no hidden costs.

181 / 280

Different artifacts, different rooms

One ship, written for three rooms.

Peers & builders
X threads · essays · the log
They come for the craft and the mechanism. The currency is ideas, and the payoff is reputation — inbound by reputation.
Prospective partners
LinkedIn · case studies · docs
They come to judge whether you ship and think clearly. The currency is credibility and taste, and the payoff is an engagement.
The record & future-you
the log
The honest account of what shipped and why. It is both the archive and the source every other channel is derived from.

One voice

Every draft is held to the same brief.

Each channel is checked against the same voice before it ships — so the studio sounds like itself, not like a feed.

Sounds like

quietpluralconsideredpartner, not client

Never

passionatecutting-edgeinnovativeemoji!

Review & publish

On engagements, the room gets a vote.

For partner work, each draft surfaces inside the engagement so the team can weigh in before anything is published. Advisory only — the owner still decides.

urquhart.design/e/pye/marketing/widget

Draft preview

linkedin · rewards-selling-widget

Shipped the Pye rewards selling widget this week. Live at pye.fi/widget. The widget is the consumer-facing primitive on top of the Pye Exchange…

Team vote · advisory

Yes, ship itNot yet

example tally · owner decides

A quiet meta-note

This page came through the same engine.

Documentation, marketing, deliverables — they run on one pipeline, drawn from the same source, written in the same voice.

How the portal works →Message on X →LinkedIn →