Skip to content
signal studio

Proof

One scene. Four products. End to end.

A wedding planner sits down for the first venue call. Forty-five minutes later, the work is in motion across Signal Notes, Tasks, Timeline, and Signal. This page is that scene, layer by layer.

The example is wedding planning because it is real. The pattern holds for anyone who runs work that has a deadline, real money, and people who need to read the plan without being trained on a tool.

Signal Notes · Capture clarity

The venue call.

The planner sits in a venue meeting. Everything lands in Notes.

Forty-five minutes. Vendor names, deposit amounts, the date the bride wants confirmed by Friday, the venue coordinator's worry about the marquee plan if it rains. Some of it will turn into tasks. Some of it is just thinking out loud. Notes does not sort yet.

Notes is private by design. Nothing leaves until the planner decides what does. The empty page is a protected writing space, not a collaboration surface.

From the planner's notebook
  • Venue confirmed, Powerscourt, Saturday Sept 26.
  • Florist: Bloom & Co. Quote sent. Waiting reply.
  • Marquee: only if rain forecast. Decide by 14 days out.
  • Bride: wants save-the-dates posted by July 15.
  • Catering: need final headcount by August 1.
  • Tom (groom's dad), does the toast. Mention to MC.
  • Coordinator on the day: Aoife.

Outcome · 12 captures. 3 ready to promote into Tasks.

Signal Tasks · Execution clarity

After the meeting.

Three notes become three tasks. The wedding workspace takes shape.

The planner long-presses three captures. Each one promotes into a task in a fresh wedding workspace. Tags do the job that projects would do in a heavier tool, "florist" becomes a project, "venue" becomes a project, "save-the-dates" sits inside print.

The workspace was seeded from the canonical wedding template, so the structure is already there. The planner did not configure anything.

Workspace · Sarah and James, Sept 26
  • Confirm florist quote, florist · waiting on Bloom & Co
  • Decide marquee yes/no by 14 days out, venue · scheduled
  • Send save-the-dates by July 15, print · doing
  • Final headcount to caterer by Aug 1, catering
  • Brief MC on Tom's toast, ceremony

Outcome · 3 tasks promoted. 4 tags. 0 setup.

Signal Timeline · Direction clarity

Same evening.

One link goes to the couple. The plan is now public to them.

The planner publishes a Timeline update from the same workspace. Public link. Plain English. No private notes. No vendor pricing. Just the milestones the couple care about and the next decision they have to make.

The couple read it at midnight on their phone. No login. No app to install. No tax on their attention.

Public timeline · sarah-and-james.signal.example
  • Now → Save-the-dates by July 15
  • Next → Final headcount by August 1
  • Then → Confirm florist (waiting on quote)
  • Soon → Decide marquee 14 days before the date
  • Held up → Catering, need your guest list first

Outcome · One link the couple can read at midnight. No login.

Signal · Attention clarity

The next morning.

At 6am, the briefing names what needs the planner's attention.

Signal reads the state of the workspace overnight. Ten rules look for held-up work, overdue items, quiet projects, and concentration of work on one person. Three items per block. Always three. Silence is signal too.

Every sentence is drawn from a curated library written by hand. No LLM in the path. The briefing tells you what changed; it does not decide what you should do about it.

Today's briefing · Tuesday morning
  • Needs attention
  • Florist quote has been quiet for 8 days, and Confirm florist is held up by it.
  • Save-the-dates were due 3 days ago.
  • Suggested focus
  • Chase Bloom & Co today, Confirm florist is waiting on them.
  • Close out save-the-dates today, they're 3 days late.

Outcome · Two minutes of reading. The day is shaped before the inbox.

The point

Not all-in-one. Four products, doing one job each, with the boundaries between them written out loud.

Most productivity tools ask you to do the translation work yourself: between the meeting and the task list, between the task list and what the customer sees, between what you shipped and what you do tomorrow. Signal Studio holds the translations so you do not have to.

The suite is four small tools that already know how to talk to each other. Notes promotes to Tasks. Tasks publishes to Timeline. Tasks feeds Signal. The handoffs are the product.