BOT Chain · Delivery × BD

Delivery Role
& BD Collaboration

Delivery does not own lead gen or commercial promises — and does not add extra form work for BD. BD owns the deal; Delivery owns execution. Standard questions and go-live materials stay with Delivery.

Role How we help BD How to work together Internal training
Intake
One door for delivery requests
Handle directly, or lead cross-team work
Less load
Fewer repeat asks & chase-ups
Standard FAQ → Delivery / Bot
Close loop
Post go-live materials complete
Form · Logo · Wallet · sync
01 · Role

Where Delivery sits

Clear role first — then collaboration works.

Definition

The single intake for BD delivery needs

We take project / BD delivery asks: finish what we can; lead cross-team work when needed; turn repeat questions into standard answers.

Delivery is not sales. We do not make commercial commitments for BD.
1–2

Intake · Route

  • Collect access, deploy, materials, and progress asks
  • Decide: Delivery alone vs tech / marketing / finance / ops
3–4

Drive · Capture

  • Join chats, help access / deploy, unblock until done
  • FAQ + Bot for routine questions
5–6

Close · Align

  • After go-live: status, form, logo / wallet
  • Lead cross-team sync so BD is not the middleman
Delivery is BD’s delivery door — not a second sales team. Intake → route → drive → capture → close.
02 · Value for BD

Four ways we help

What Delivery takes off BD’s plate.

01 Questions

Fewer repeat DMs

Access / deploy / progress questions go to Delivery or the group Bot first.

02 One voice

Consistent answers

Shared FAQ and scripts — less improvised, less mismatch.

03 Execution

BD stays on the deal

We join, unblock, and chase delivery. BD keeps the relationship.

04 Close loop

Less middleman work

Status, Google Form, logo / wallet chase, and push to finance / ops / tech — plus cross-team coordination.

BD brings the project and owns the relationship. Delivery owns execution and the close-out.
03 · Delivery Bot

What it does / doesn’t

A delivery tool in the group — not chat, not deal-making.

Does
  • Answers standard deploy / access questions
  • Welcomes new project groups
  • Sends the form after go-live and collects logo
  • Supports daily / weekly delivery reports
Does not
  • Quote, contract terms, or listing promises
  • Replace BD commercial judgment
  • Work if not invited to the group
  • Force-match projects when the group name ≠ Lark project
BD decides commercial calls. Standard tech questions stay in-group with Delivery + Bot.
04 · BD rules

Five habits that keep the Bot working

Create the group right, invite the right people, align names, keep roles clear.

1 Group

Own Telegram group + invite Delivery

Invite @Roy4by4. No invite → no welcome, FAQ, or form send.

2 Naming

Match the Lark project name

Use the official project name (or include it clearly). Avoid “test”, vague “collab”, or nicknames only.

3 Ask in-group

Standard questions stay in chat

Guide partners to ask access / deploy in the group — less private-chat forwarding.

4–5 Go-live & form

Hand off go-live; chase, don’t fill

“Project is live” is for Delivery ops. After BD confirms readiness, hand off. Nudge partners to fill the form — don’t fill key wallet fields for them.

Create group → invite Delivery → align name → ask in-group → hand off go-live → partner fills the form.
05 · SOP

Eight steps, clear owners

BD owns the door and the nudge. Delivery owns execution and close-out.

01

BD creates group

Invite Delivery account + teammate

02

Delivery intake

Help with ecosystem app access

03

Bot Q&A

Standard deploy questions in-group

04

Confirm live

Delivery confirms go-live

05

Update status

Lark status / ops command

06

Send form

Google Form to the group

07

Write back

Partner fills → sync to Lark

08

Notify teams

Wallet ready → finance / ops / tech

BD owns

Create & invite, name match, raise delivery needs, chase partner form fill.

Delivery owns

Intake, Q&A, status, form loop, cross-team sync.

06 · Boundary

Who owns what

Clear lines → less overlap and finger-pointing.

Delivery BD
Intake, access, close-out, one voice on delivery topics Leads, commercial talks, relationship, deal judgment
Deploy follow-up, status, materials chase Create group, invite people, keep names aligned
FAQ / Bot voice; lead cross-team delivery work Commercial promises & external commercial voice; route cross-team asks to Delivery first
Accountable for delivery outcomes Accountable for the relationship & commercial result
Delivery does not replace BD’s commercial call. BD does not replace Delivery’s go-live confirm. The Bot is a Delivery efficiency tool.
07 · Takeaways

Remember three things

Align on these before diving into edge cases.

Role

Delivery is BD’s delivery door

Not a second sales team.

Value

Intake · one voice · close loop

Less explaining, chasing, and cross-team ping-pong for BD.

Habits

Group · align · ask in chat

Hand off go-live; partner fills the form.

Create group → invite Delivery → align name → ask in-group → hand off go-live → partner fills the form.
Quick FAQ
  • Skip inviting Delivery? No — FAQ and auto-form need the account in-group.
  • Exact name match? Match or clearly include the official project name.
  • Who quotes? BD. The Bot never quotes.
  • Can BD send “project is live”? Usually no — hand off to Delivery.
1 / 8