b buddy research preview sign in

a digital intern
for the whole team.

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.

it's a group chat

the whole team, one thread.

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.

# halden-pilot spdb #slack@email▢app replay
message # halden-pilot
buddy's todos 0 open
nothing yet
computer idle
about:blank
waiting for work
its own inbox

cc it like anyone else.

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.

client questionteam requestnew leadcontract to sign
came in · email
fromrachel okafor · haldenhealth.com
toyou
cc[teammate]@[company].trybuddynow.com
re: pilot terms and seat counts

before we sign, can you confirm seats through q1 and what happens if we add a fourth clinic?

what it did

pulled the seat numbers and the pricing sheet, and drafted the reply. seat counts touch pricing, so it goes to dev first.

to rachel okafor · cc you

42 seats today, and we'll hold 50 through march at the current rate. a fourth clinic would add 12 seats on the same terms. the updated order form is attached.

waiting on dev's yes decline approve
show it once

teach it the way the team does it.

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.

teaching · netsuite you have the keys
reports · saved searches
you said ›not the invoice list. it stops at 1,000 rows. ›csv, always. priya's import hates excel. ›(edited draft) seat counts before price when writing to rachel.
buddy wrotelearned from your edit export invoices from netsuite
1reports → saved searches ·gotcha: not the invoice list, it caps at 1,000 rows 2last month, first to last day 3export as csv 4email priya the row count
saved to memory
buddy's computer · mail.google.com/…/thread/pilot-terms buddy has control
mail.google.com/mail/u/0/#inbox/pilot-terms
re: pilot terms reply
buddy>tell buddy what to do on this screen…
view only. take over to interact. take over
a real computer

watch the screen live. take the keys anytime.

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.

settings · teamon the team
dev mehtaceo · northloop picks up on its own
sam ortizops lead · northloop picks up on its own
rachel okaforprocurement · halden health asks you first
mara lindqvistpartner · fjord legal asks you first
tap a row to switch it
in or out

your team hands it work directly.

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.

it knows the job

its own notes on the work.

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.

memory · people6
rachel okaforclient · halden healthpilot terms, seat counts. signs off over $10k.
priya nairteammatebooks and invoicingquickbooks, the monthly close. out fridays.
dev mehtaownernorthloopthe board deck, final say on pricing.daily update.
reconcile invoices against quickbooksstep 2 of 3
1import the month's csv 2match on amount and date, within 3 days ·gotcha: partial payments come in as two lines
v2 · edited by buddy, sep 24
books & invoicing · per month$30 / working hr
may 6 procedures saved 87 h $2,610
jun 19 procedures saved 78 h $2,340
jul 31 procedures saved 70 h $2,100
sep 44 procedures saved 60 h $1,800 same workload as may, $810 less
it gets faster

the fifth time isn't the first.

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.

plan

it plans. whoever asked approves. then it runs.

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.

plan v2
goalanswer the weekend's mail, drafting replies for your approval rather than sending them.
done whenevery thread is answered, filed, or waiting in approvals with a draft attached.
missing?is there a deadline i should work against?
update the plan approve and run
waiting on priya · 2h
stuck on the vendor export. priya, i need you to log in.
computer paused at the sign-in screentake the keys
waiting on dev · 20m
the quote to rachel is still open. dev, want me to send it? not now yes, send it
stuck means ask

it doesn't quit.

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.

approvals first

nothing leaves without a yes from the person who asked.

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.

gmail · to rachel@lumen.co · asked by dev send
send the reply about pilot terms? she asked for a number by tuesday. i drafted the seat-count hold through the quarter.
decline approve
▸triage/4
·plan.md1.2 kb
·backlog.md4.1 kb
·drafts/rachel.txt812 b
▸notes/2
drop files into a linked folder
a filesystem that survives

the work is still there next week.

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.

your apps, connected

click through the apps buddy can touch.

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.

connected: gmail, slack, linear
✓ Gmail 12 tools
✓ Slack 9 tools
✓ Linear 11 tools
GitHub 14 tools
Notion 10 tools

give buddy a seat.

it'll still be at the desk when anyone checks back.
and it'll know the job better than it did yesterday.

▶get started
need it for a larger team? contact us about enterprise plans.
approvals firstdisposable computedurable storage