Projects that
start themselves.
RESK is where the work happens — milestones, tasks, owners, and client updates. It just happens to know where the work came from, so a won deal arrives as a running project instead of an empty one.
- Milestones, tasks, owners, and due dates
- Drafted the moment a deal is won
- Slack channel opened with a kickoff post
See it on your pipeline
A 20-minute walkthrough with the team that sets your workspace up.
- We create your workspace and first admin
- Your team joins by invite — no shared passwords
- Bring the leads you already have
Provisioned per company. No open signup.
Teams closing and delivering on RESK
Six modules, one set of records.
Delivery work, the accounts behind it, the automation around it, and the tools your team already has open all read and write the same records — so nothing is re-entered at a handoff, and nothing drifts out of sync.
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-app and in their browser.
Kickoff & discovery
Confirm scope with Dana Ruiz
2Aug 18Collect current routing data
Aug 19Implementation
Configure two depot regions
3Aug 22Import driver roster
1Aug 25Run the delivery, not just the deal.
Milestones hold the phases, tasks hold the work, and every task carries an owner, a due date, and a comment thread. Progress is whatever the tasks actually say it is — nobody updates a status field by hand.
Milestones with real progress
Each phase reports from the tasks inside it, so the bar can't drift from the work.
Assignee, due date, comments
On every task — and assigning or commenting notifies the owner immediately.
Collaborators, not just owners
More than one person can work a project without taking it over.
Blocked work surfaces instead of hiding
Harborview Logistics — Onboarding
Handover by Sep 12
In progress
2Configure two depot regions
Import driver roster
Blocked
1Client CSV outstanding
Done
2Confirm scope with Dana Ruiz
Collect routing data
The project builds itself.
One status change starts everything: RESK reads the whole conversation, drafts milestones and tasks, assigns them to the rep who owned the deal, and opens a Slack channel with a kickoff summary. No handoff meeting, no blank project.
The plan comes from the conversation
Milestones and tasks are drafted from the notes and calls already on the record.
Assigned to a real person
Work lands on the rep who closed it, never in an unowned queue.
Slack channel and kickoff post
Skipped and logged if Slack isn't connected — the rest still runs.
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.
Told once, in both places.
Assignments, comments, Slack mentions, and finished reports all run through a single call that writes the in-app notification and fires the browser push together — so one can never show up without the other.
One dispatch, two destinations
The row and the push are written together — one can't exist without the other.
Push through the service worker
Reaches the browser even when the tab is closed.
Click through to the record
Marks read and opens the task or project it came from.
Triggers
- Task assigned
- Task commented
- Slack mention
- Report ready
RESK · now
ChromeTask assigned to you
Confirm scope with Dana Ruiz — Harborview Logistics
Notifications
4Priya assigned you “Confirm scope with Dana Ruiz”
Task assignedIn-app + push
You were mentioned in #harborview-onboarding
Slack mentionIn-app + push
Weekly report drafted for Northwind Retail Co.
Report readyIn-app + push
Marcus commented on “Import driver roster”
Task commentedIn-app only
The front door to all of it.
Work has to come from somewhere. Leads, companies, and contacts live in the same workspace as the delivery, so the account you sold is the account you deliver to — and nothing is re-entered at the handoff.
Leads through to Closed
New, Contacted, Qualified, Referral, Follow-up — with notes and calls on the record.
One account record
The company and its people carry through from first contact to final invoice.
Sequences when you need them
Scheduled multi-step outreach, sent to the same contacts the projects use.
Pipeline by status
128 leads
Needs follow-up today
3 waitingSunrise Dental · history
Source: ReferralCall — Asked to check back after their board meeting
4d agoNote — Referred by Harborview — warm intro over email
9d agoEmail — Sent capability overview and pricing bands
12d ago
AI writes the draft.
A person signs it off.
Anything a customer will read is computed from real project state, never generated. Anything generated stops at a draft until someone on your team approves it. The line between the two is drawn in the product, not in a policy document.
Written by AI
Internal project report
Assembled from active tasks, the Gmail thread, and the Slack channel. The model proposes a status — approving it is what makes it real.
Human approval required
Harborview Logistics — Onboarding
Weekly progress report
The model proposes a status. It never sets one.
No model involved
Client update email
Rendered from milestone and task state through your own template. Deterministic, so there is nothing to hallucinate and nothing to review.
Sends without approval
Harborview Logistics — weekly progress
To dana.ruiz@harborview.co
Hi Dana — here is where the onboarding stands this week.
- Kickoff & discoveryComplete
- Implementation2 of 3 tasks done
- HandoverNot started
Training is booked for next Tuesday. Reply here if anything looks off.
Computed, not written. Nothing to review.
Sent 09:00What actually happens on Closed/Won.
One status change, five steps, no orchestration to babysit. Click any step to see what it does — and what happens when a piece isn't connected yet.
Who sees what, decided in two layers.
A route-level gate decides whether a module is reachable at all. Row-level scoping then decides which records inside it a person actually sees. Both run on every request.
01
Company ceiling
Modules switched off for the company are unreachable first — checked before role, so nothing inside the company can widen it back open.
02
Role & override
Admins and super admins pass. Everyone else is measured against their access role, or a per-module override set just for them.
03
Row-level scope
Past the gate, reps still only see rows they own, are assigned, collaborate on, or share a team with. Admins see everything.
Access roles
Fieldstone workspaceAssigned work only
Leads
EditProjects
ViewTasks
EditReports
ViewBilling
DisabledClick a module to switch it off for the whole company. The company ceiling is checked before role — no override inside the company reopens it.
Rows returned
Own + assigned + collaborator + team
Reporting your team already trusts.
Leads, task completion, active sequences and workflows, project status, and billing — read straight off the records your reps work every day. There is no second reporting system to keep in sync.
Total leads
128
18% win rate
Task completion
42%
92/220 tasks
Active sequences
7
9 total
Active workflows
5
8 total
MRR
$1,430
Growth plan
Seats used
9
of 15
Invoiced amount
Trailing 12 months
Leads by status
Current pipeline distribution
Connected to what your team already runs.
Calendars, mail, Slack, and outbound email are wired into the records themselves — a project pulls its own Gmail thread and Slack channel when it writes a report.
Google Calendar
Meetings sync to Home
Microsoft Graph
Outlook calendar alongside Google
Gmail
Read-only thread context on projects
Slack
Project channels, kickoff posts, mentions
SMTP
Sequence sends and client updates
Web Push
Browser notifications via service worker
Google & LinkedIn
OIDC sign-in for your team
Claude (MCP)
Scoped task access from Claude Desktop
Work your tasks from Claude.
Generate a personal access token, run the setup script, and RESK shows up as an MCP server in Claude Desktop or Claude Code. It authenticates as you — and only reaches what the token is scoped to.
Settings → Developers → generate token
Tokens are yours, revocable, and carry your real role underneath.
Scoped at the routing chokepoint
Tasks CRUD plus read-only projects. Not a wider key with rules bolted on after.
claude_desktop_config.json
{ "mcpServers": { "resk": { "command": "python", "env": { "RESK_PAT": "crm_pat_·······" } } }}What the token can reach
list_tasksTaskscreate_taskTasksupdate_taskTaskslist_projectsProjects · read-onlyEverything else is refused before the user is even resolved — including minting more tokens.
How teams close the gap
between sold and delivered.
The handoff is the bug
Every team we talk to has the same gap: the deal closes on a Friday and the delivery work starts the following Wednesday, after someone rebuilds the context from scratch. We stopped treating that as a process problem and made it a product one.
Priya Nandan
Product · Aug 12, 2026
- 01ProductAug 5, 20264 min read
Why AI never writes your project status
The model drafts. A person decides. Here is the reasoning behind holding every generated report at a draft.
- 02EngineeringJul 28, 20267 min read
Permission checks that cannot drift
One implementation for the HTTP layer and the agent tools — and what broke before we had it.
- 03AutomationJul 19, 20265 min read
Unsubscribe is the only exit we trust
Reply detection sounds useful until it silently stops a sequence it should not have.
The day a lead goes to Closed/Won, the project, the tasks, and the Slack channel are already there. Nobody has to remember to build them.
Avery Chen
Sales Manager, Harborview Logistics
No open signup. On purpose.
Workspaces are provisioned, not self-served — so there is no unclaimed account holding your customer data, and no admin emailing passwords around.
- 01
We create your company
Your workspace and its first admin are set up for you — no self-signup, no unclaimed accounts.
- 02
Your admin sets a real password
The owner-chosen password is forced out on first login before any data loads.
- 03
Everyone else joins by invite
Teammates get a magic link, set their own password, and land signed in. Admins never handle a password.
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.