The won deal builds its own project.
Moving a lead to Closed/Won is the one status change with real side effects. RESK reads the whole conversation, drafts a milestone and task plan, assigns it to the rep who owned the lead, and opens a Slack channel with a kickoff summary.
- status change
- 1status change
- handoff meetings
- 0handoff meetings
- milestones drafted
- 3milestones drafted
Harborview Logistics
Owner · Priya Nandan
Harborview Logistics — Onboarding
3 milestones · 5 tasksDrafted from 14 notes and 3 calls on the lead
Kickoff & discovery
- Confirm scope with Dana Ruiz
- Collect current routing data
Implementation
- Configure two depot regions
- Import driver roster
Handover
- Train dispatch team
harborview-onboarding
RESKjust now
Harborview Logistics is now a customer 🎉
Project created with 3 milestones and 5 tasks, owned by Priya Nandan.
The path a record actually takes.
- 01
The lead is marked Closed/Won
A single PATCH on the lead record starts everything below.
- 02
The conversation is read
Notes, calls, and referral history from the whole lead go to the model, which returns a proposed milestone and task breakdown.
- 03
The project is created
Milestones, tasks, and assignments land on the rep who owned the lead — never in an unowned queue.
- 04
Slack is opened, if it can be
Channel created, team invited, kickoff summary posted. If Slack is not connected the step is skipped and logged; nothing else fails.
Work that lands on a person.
Every task carries an assignee, a due date, and a comment thread, and rolls up under the milestone it belongs to. Assigning or commenting notifies the owner in both places.
Kickoff & discovery
Confirm scope with Dana Ruiz
2Aug 18Collect current routing data
Aug 19Implementation
Configure two depot regions
3Aug 22Import driver roster
1Aug 25What you get.
Milestones
Phases of delivery, each holding the tasks that belong to it.
Tasks with owners
An assignee, a due date, and a comment thread on every one.
Assignment notifies
Assigning or commenting reaches the owner in-app and in their browser.
Slack channel per project
Created on win, with the team invited and a kickoff summary posted.
Plan drafted from real history
The breakdown comes from the conversation, not from a generic template.
Collaborators
More than one person can work a project without owning it.
Never rebuild the same project twice.
We set up your workspace and your first admin. Your team joins by invite, and the next deal you close arrives as a project that is already moving.
- We set up your workspace
- Your team joins by invite
- Bring the pipeline you have
Prefer to talk first?
- 01
Deal marked Closed/Won
One status change
- 02
Project, milestones, 5 tasks
Drafted from the conversation
- 03
#harborview-onboarding
Channel opened, kickoff posted
- 04
Owner notified
In-app and browser push
Every step above runs from one status change.