Your best work.Surfaced when it counts.

Pulsework helps you keep a private work record and prepare drafts from it. Email and the web app come first.

A few messy sentences about your day, with your goals alongside. Your long-term goals guide the morning plan and the evening account.

The first release is for invited users. Features are being built in stages; the examples below show the planned experience.

Morning plan For you

A plan shaped by your goals and what is still open.

Evening account Draft · for review

Your notes, what moved your goals, and what is still unknown.

Before your 1:1 Draft · held

An update from days you approved, ready for you to review and copy.

Approving a day and sharing an update are separate choices. Nothing goes to another person without your approval of that exact document and recipient.

Start with Pulsework

Continue to sign up. Add your notes in Pulsework, where you can see what was saved.

The first release is for invited users.

A fair question

What did you get done the week of March 9th?

Exactly.

Good work is easy to lose in a busy week. Your notes and approved days keep the details together, so you can return to what happened and prepare your next update.

Sign up

Your record · week of March 9th Product preview
Built from 4 approved days
✓
Payments architecture: direction settled, approved, delivered to the team.
Your approved days record the decision and when you shared it.
Your Monday note: three PRs merged Your Tuesday note: design deck drafted Your Tuesday note: shared with the team Approved day: architecture decision
High impact, low visibility
·
Settled two interface decisions before implementation; cleared four review threads that were holding others.
~3 hrs across the week. None of it was a ticket. All of it stayed on the record, with dates.
Carried forward, honestly
Retry semantics stayed unresolved. No progress claimed; the open matter stayed in the record.
1:1 update drafted Approved days linked Notes linked Held for review
Planned record view. Illustrative notes, not a connected-tool feed.

The record compounds

Your work story,
built a day at a time.

Your notes become an evening account you can review. Approved days support the next 1:1 update and stay available to return to later.

Today· the record starts working
Evening accountDraft · for review
  • What happenedPayments migration merged; Sam’s retry review completed.
  • What is nextCutover preparation.
  • Still unknownWhether staging access was restored.

Review and edit the draft before approving that day. Approval does not send it to anyone.

Before your 1:1· approved days become an update
1:1 update for DanDraft · held
  • Architecture direction delivered - settled, approved, shipped to the team. Your approved Monday and Tuesday days
  • Four review threads cleared - others unblocked, on the record.
  • Retry semantics carried forward honestly - flagged, not dressed up.

Built from days you approved. Review and copy the exact version you choose.

Over time· your record stays useful
Your recordApproved days and notes
  • Reopen the exact day you approved.
  • Search your record by keyword.
  • See dated corrections beside the original.

Your work stays available while your account is active, under the privacy policy.

It comes to you

Email and the web app first.

The first invited release brings the daily loop to email, the web app, and your own Claude. Slack follows, with your choice to connect.

How did today go?
From Pulsework <hello@pulsework.co> · To you · 5:30 PM
Reply to this email - messy is fine.
finally merged the payments migration. reviewed sam's retry thing for maybe an hour. flaky test still went nowhere
- your reply, 5:34 PM
Your day, ranked - draft, held.

✓ Merged the payments migration.
Prerequisite for the cutover on your sprint goals.

Unblocked Sam on webhook retries (~1 hr) - on the record.

Flaky test - aligned, not yet impactful. Kept honest.

Your note is saved. This day is a draft until you review and approve it. You can add another note by replying.

Planned first-release email flow. Reply with notes; review and approve through the app or an available email approval step. Sending an update needs its own approval.

ADMs
Pulsework direct message · only you
PW
Pulsework8:40 AM
Morning. The cutover is the priority in your plan. What changed since your last note? Example: full brief in the app
A
you8:47 AM
Sam’s review is done. I’m keeping the afternoon for the cutover.
PW
Pulsework8:47 AM
Your note is saved. Review your day in Pulsework before approving it.

Coming soon. Slack carries prompts, replies, short notes to Pulsework and STOP. Review and approval stay in email or the app; no channel mentions or workspace archive are read.

One private record. Email and the web app first.

When you want the whole record, Pulsework has a place for that too.

The web app is part of the first release. Use it to review and approve days, inspect your record, add a dated correction, and copy an update.

Your record · week of July 14 · 4 days
MonCutover plan drafted; checklist to Marcus. 2 items · 1 confirmed win
TuePayments migration merged. Sam unblocked. 3 items · ⚑ 1 open
W–ThNo notes supplied. The day says what is not known.
Fri1:1 update copied for Dan. Exact copied version kept
Planned record view. Illustrative data.

Why it's trustworthy

It asks before it claims.

Pulsework is designed to rank work against your goals, label inferences and ask before presenting an inferred win as confirmed. You review the draft for mistakes.

Before Pulsework claims it
Marcus's PR looks like more than a review - your Tuesday note would make it the last open dependency on the sprint's deliverable. That link is an inference from your note, not a verified fact.
Aligned, not yet impactful
Work without a supported outcome stays recorded as effort.
Illustrative confirmation step. This example does not change a record.

Your day is a draft until you approve it. Sharing an update is a separate choice.

Ranks, doesn't flatterThe morning plan and evening account relate your work to your stated long-term goals and this week’s objectives. When the work drifts, the draft says so.
Inference is labeledWhen Pulsework connects dots, it says so, shows the source, and asks. Confirmed wins carry your confirmation; declined ones are why the rest get believed.
Effort stays honestWork that has not landed stays recorded as effort. A draft should not claim an outcome that your notes do not support.
You control what leavesNothing is sent to another person without your approval of the exact document and recipient.

How it works

Your notes become a day you can review and an update for your 1:1.
You decide what gets shared.

You type what happened

In email or the app. A few messy sentences are enough to begin.

Your day comes back ranked

Against your goals, with a short explanation and the supporting notes. You review it and confirm inferred wins before they are presented as confirmed.

Before your 1:1

A draft from days you approved, held for you to review and copy. Sending is a separate choice when it is available.

Day-close · 5:30 PM prompt, your 5:34 PM reply

Day’s over. What happened? A few messy sentences. I sort, you don’t perform.

finally merged the payments migration. reviewed sam's retry thing for maybe an hour. flaky test still went nowhere

Kept verbatim in your record - corrections append, nothing is silently rewritten.

Planned flow. Illustrative data.
Your day, ranked by what mattered · draft, held
✓
Merged the payments migration.
Prerequisite for the cutover on your sprint goals. That is why it leads.
2
Unblocked Sam on webhook retries (~1 hr).
Third unblock this sprint. On the record.
Aligned, not yet impactful
Flaky test: no movement reported. It stays in the record without a claim of progress.
Draft - held Your note is saved. Approve the day after reviewing it. Sharing is separate.
Planned flow. Illustrative data.
1:1 update for Dan · prepared before your meeting Draft - held for you
What moved
Merged the payments migration; Friday’s demo runs on it. (from your Mon–Tue days)
Unblocked Sam on webhook retries - third unblock this sprint. (on the record, with dates)
Still open
The flaky test - effort spent, no movement yet; flagged before it bites the release. (kept honest, not claimed)
Every line traces to a day you approved. Review and copy the exact draft; send only through an available approval path.
Planned flow. Illustrative data.

The payoff

Your next 1:1 starts with a record.

Approved days give you a draft of what moved, what remains open and what you need to discuss. Review it, edit it and copy the exact version you choose.

Sending from your mailbox is separate and available only when that feature is enabled.

1:1 update for Dan · from approved days Draft - held for you
What moved
The payments migration merged. Sam’s retry review is complete. (Your approved Monday and Tuesday days)
What remains open
The flaky test has not moved. No progress is claimed. (Your latest note)
For the conversation
What needs attention before the cutover? (Draft question for you to edit)
Review before sharing. Copy keeps the exact version; it does not prove delivery.
Planned 1:1 draft. Illustrative data.

Early access

The first invited release.

Email and the web app come first. Features are being introduced in stages.

For invited users
No billing in this release
Private notes, days you review and approve, and an update for your 1:1. Slack follows.
Paid plans, team reports and review packets are later work. The privacy policy governs what you can export and how long information stays.

Fair questions

Asked and answered, plainly.

Why keep a work record here?
Pulsework is being built around your notes, approved days and goals, so the next draft has a record to draw from. It reads your mail only if you connect it, and then keeps what it learned, not your messages. It does not collect your AI conversations. Email and the web app are the first invited release.
How much time does this take, really?
Start with a few messy sentences about what happened. Typos are fine. You still review the draft, correct anything wrong and choose whether to approve it.
What is the evening draft meant to contain?
An account of what happened and how it relates to your goals, with supporting notes and anything still unknown made clear. An inferred win needs your confirmation. Pulsework may ask one clarifying question. If writing is unavailable, it can show your notes in the order you wrote them, clearly labelled, for you to edit.
What if I skip days?
An unanswered morning or evening can get one reminder after thirty minutes; the wait is adjustable. Reading alone does not cancel it. Quiet hours, pause and stop still apply. Pulsework starts at most six messages a day across all channels, with replies you ask for counted separately. Contact gets quieter over time if you stop replying, and returning does not trigger a backlog.
Where does it learn about my work?
From notes and goals you give Pulsework. If you connect your own Claude, it can read your day where your work happens and hand Pulsework a short account of it; what it sends is listed in the privacy policy. When offered, an optional Google connection can read calendars you choose, or read new mail and keep a short account of it. Each is its own permission, and sending from your Gmail is a third. You can use notes, manually entered meetings and Copy without Google. Pulsework reaches you by email. Native Claude, ChatGPT, Slack and text messaging connectors coming soon.
Will it exaggerate what I did?
It can make mistakes. Pulsework is designed to show supporting notes, label an inference and ask before treating an inferred win as confirmed. Work without evidence of an outcome should stay uncertain. You review and correct the draft before approving or sharing it.
Who sees what I write?
Your employer or manager does not get routine access to your private notes, even if an employer pays. Providers process information needed to run the service, and limited, recorded operator access may be needed for a repair. Sharing a document requires your approval of that exact version and recipient. The privacy policy explains access, retention, removal and the reviewed career export.

Two or three sentences about today. That's the whole start.

Start with your own notes. Review the draft and choose what to keep.