{{ legalTitle }}
{{ legalIntro }}
{{ c.n }}{{ c.h }}
{{ p }}
questions
write to trybuddynow@gmail.com.
buddy has its own inbox and its own desk. email it, slack it, or sit next to it and show it. it asks the person who'd know when it's stuck, and nothing goes out until the person who asked says yes.
sam's on slack, priya emails, dev opens the app. it's all one thread to buddy. it answers each of them where they asked, by name, and keeps their asks straight, learning along the way.
client email lands in the thread too. when buddy needs a decision it asks the person who owns it, and nothing goes out until they say yes.
it has its own email and slack. clients, vendors and your team write to it like a coworker. your team can hand it work directly. anything going to someone outside waits for the right person to say yes.
priya does it once. after that buddy does it for everyone.
do it yourself, say what matters as you go, hand back. buddy writes it down and does it that way next time, for whoever asks. anyone on the team can read it, edit it, or throw it out.
buddy drives a full desktop and browser, not an api shim. watch every click as it happens, expand the screen to half or full width, double-click to take over, and hand back when you're done. hand back and buddy knows what you did while you had the keys. type into the bubble to steer without touching anything.
put the people you trust on the team. their emails and mentions become work buddy picks up on its own, no one has to open the app. for everyone else, it reads the message and asks you first. sends and payments still wait for a yes either way.
people, how things are done here, and what's going on.
who's on the team and what they own. who the clients and vendors are and how they like things. how this team does each thing. what buddy is on right now and for whom. all of it in settings, all of it editable, and everyone on the team sees it write.
the first time, it asks. every answer and every edit becomes a saved procedure, so the list of things it already knows how to do keeps growing and the same work takes fewer hours. same job, less of everyone.
press plan and buddy drafts a plan first: the goal, what done looks like, the inputs it has, and the questions it still needs answered. ask for changes over as many rounds as you like. nothing runs until you say so, and the approved plan is saved to your project as plan.md.
when it's stuck, it asks the one person who'd know, and waits.
minutes or days, the computer stays paused. if priya's the one with the login, priya gets the question, not everyone. and when the desk is quiet it looks at what's open and asks whoever's around if it should take the next thing.
sends, posts, and payments stop and wait, with the exact plan and tools on the card. the card goes to whoever gave buddy the job. nobody else's yes counts. stop a run mid-flight and it holds at the boundary. resume with a note, or cancel for good.
files live in a store that outlasts any session. projects link the folders they need, drafts and notes accumulate, and the next run picks up exactly where the last one held. drag files in, rename, edit, and read everything buddy writes. every file is the team's, not one person's.
gmail, slack, linear, github, notion and more. turn them on per session from the chat bar. apps that need a login, one person authorizes once in settings and the team is set.
it'll still be at the desk when anyone checks back.
and it'll know the job better than it did yesterday.
{{ legalIntro }}
{{ p }}
write to trybuddynow@gmail.com.
buddy has its own inbox and its own desk. email it, slack it, or sit next to it and show it. it asks the person who'd know when it's stuck, and nothing goes out until the person who asked says yes.
sam's on slack, priya emails, dev opens the app. it's all one thread to buddy. it answers each of them where they asked, by name, and keeps their asks straight, learning along the way.
client email lands in the thread too. when buddy needs a decision it asks the person who owns it, and nothing goes out until they say yes.
it has its own email and slack. clients, vendors and your team write to it like a coworker. your team can hand it work directly. anything going to someone outside waits for the right person to say yes.
priya does it once. after that buddy does it for everyone.
do it yourself, say what matters as you go, hand back. buddy writes it down and does it that way next time, for whoever asks. anyone on the team can read it, edit it, or throw it out.
buddy drives a full desktop and browser, not an api shim. watch every click as it happens, expand the screen to half or full width, double-click to take over, and hand back when you're done. hand back and buddy knows what you did while you had the keys. type into the bubble to steer without touching anything.
put the people you trust on the team. their emails and mentions become work buddy picks up on its own, no one has to open the app. for everyone else, it reads the message and asks you first. sends and payments still wait for a yes either way.
people, how things are done here, and what's going on.
who's on the team and what they own. who the clients and vendors are and how they like things. how this team does each thing. what buddy is on right now and for whom. all of it in settings, all of it editable, and everyone on the team sees it write.
the first time, it asks. every answer and every edit becomes a saved procedure, so the list of things it already knows how to do keeps growing and the same work takes fewer hours. same job, less of everyone.
press plan and buddy drafts a plan first: the goal, what done looks like, the inputs it has, and the questions it still needs answered. ask for changes over as many rounds as you like. nothing runs until you say so, and the approved plan is saved to your project as plan.md.
when it's stuck, it asks the one person who'd know, and waits.
minutes or days, the computer stays paused. if priya's the one with the login, priya gets the question, not everyone. and when the desk is quiet it looks at what's open and asks whoever's around if it should take the next thing.
sends, posts, and payments stop and wait, with the exact plan and tools on the card. the card goes to whoever gave buddy the job. nobody else's yes counts. stop a run mid-flight and it holds at the boundary. resume with a note, or cancel for good.
files live in a store that outlasts any session. projects link the folders they need, drafts and notes accumulate, and the next run picks up exactly where the last one held. drag files in, rename, edit, and read everything buddy writes. every file is the team's, not one person's.
gmail, slack, linear, github, notion and more. turn them on per session from the chat bar. apps that need a login, one person authorizes once in settings and the team is set.
it'll still be at the desk when anyone checks back.
and it'll know the job better than it did yesterday.