Commitment Management for Solopreneurs: Stop Reconstructing Every Promise

Have you ever finished a busy day, looked at everything you checked off, and still had the feeling that something important was waiting for you?

I have. Usually, the problem was not that I forgot a task. It was that I had made a promise, and the task list had preserved only one small piece of it.

A task is an action. A commitment is a promise.

“Send the proposal” is a task. The commitment includes what the client expects, which version was approved, what price was discussed, when the response matters, and what should happen after the client answers.

The task can be completed while the promise remains open. That is how you can do a great deal of work and still wake up trying to remember what you missed.

Write down enough to stop reconstructing it

When a promise matters, I want the record to answer six questions:

• Who did I make the promise to?
• What result are they expecting?
• When does it matter?
• What is the next action?
• Who is responsible for that action?
• What evidence will tell me the loop is actually closed?

That last question changes the quality of the work. “Follow up with the designer” is vague. “Receive the revised homepage and confirm that the approved headline is present” gives you something you can verify.

Keep the source nearby

If the commitment began in an email, meeting, voice note, or client portal, keep a link to the source. A short summary helps you scan. The source protects the meaning.

This matters after an interruption. It also matters when you delegate, because the next person should not have to act on your hurried reconstruction of what happened.

Make permission visible

A person or an AI assistant may be allowed to research, draft, organize, or recommend. That does not automatically mean they may send, publish, purchase, or change a customer’s account.

Here is the thing: approval has to belong to an exact version, action, and scope. If the work changes in a meaningful way, the old approval should not quietly follow it.

Ask for evidence, not reassurance

Consequential work should come back with something you can inspect: the published URL, the sent message, the transaction identifier, the updated record, or the before-and-after state.

That is not paperwork for its own sake. It is what lets you stop carrying the promise in your working memory.

Review the promises that still belong to you

Once a week, look for promises with no next action, work marked “done” without evidence, approvals that no longer match the current version, and dependencies that have gone quiet.

Then choose: move it forward, delegate it, renegotiate it, or close it. The point is not to preserve every commitment forever. The point is to know which promises still belong to you.

This is one of the reasons I am building Orabuena

I want the commitment, the permission, the next action, and the evidence to stay connected. Orabuena is still in private research and product discovery; I am testing this approach with solopreneurs whose businesses depend on promises that cannot afford to disappear between tools.

Which promise do you find yourself checking again and again? Tell me where the context breaks down. Research participation and product-update email remain separate choices.