Admin setup Get started AI Helper config Connect platforms Team dashboard All views

Get your team's first R&D Workforce report

Five steps · about 30 minutes of setup · then your first weekly report generates automatically 7 days from now. The two steps that need your attention are #1 AI Helper and #3 Each engineer submits — everything else is guided or automatic.

⚠ You are viewing the SAMPLE layout. To edit anything, pick your subscriber and paste your admin API key, then click Load. Without both, every button below is read-only.
1
AI Helper
config saved
2
Add team
rates + quotas
3
Each engineer submits
2 of 5 done
4
First 3-way agreement
waits on step 3
5
First report
7 days after step 3
1
AI Helper — admin configuration
Weights the 5 KPIs (rate · hours · cost · perf · quota) for your team's scoring
Done
  • Preset selected: Balanced (32 metrics enabled across 6 categories)
  • Weight sum: 100% across enabled metrics
  • Published to: wf_scheduling.ai_helper_profiles · re-scoring active
✓ Configured Adjust →
2
Team + rates + quotas
Add every engineer with their hourly rate + weekly hours target
Done · 5 engineers

Team roster · rate × weekly target sets the cost baseline.

CL
Charles Liu
$85/hr · 30h/wk · Kbot-Link + Meet3 temp assist
Set
RB
Romit Bhingradiya
$78/hr · 37.5h/wk · Kommerce-1 + AutoOMS
Set
PS
Priya S.
$68/hr · 40h/wk · newcomer
Set
HN
Haseeb N.
$72/hr · 40h/wk · Kbot Sales lane
Set
Add engineer
Sample data · load a subscriber above Manage team →
2.5
Connect your messaging pool — mandatory
Every subscriber plugs in their own delivery channel. R&D Workforce never uses its own quota to message your engineers.
Not connected

Pick one — this is where hour-ask, three-way-agreement approvals, and weekly digests get delivered to your team:

Why we don't send from our own pool: Every subscriber owns their delivery. If engineers block your webhook, complain about a message, or exceed the free tier — that's on your Slack workspace / Brevo account, not shared with anyone else. Also lets you rotate credentials and audit sends from your own admin console.
3
Each engineer submits · required for KPI accuracy
The AI Helper can't fairly propose hours it can't measure — every engineer connects OR sends a report
2 of 5 done

Two ways to submit — each engineer picks the one that matches their platform:

CL
Charles Liu
Week 38 draft pre-filled from git · confirmation pending
Draft sent
RB
Romit Bhingradiya
Awaiting Zoom reply · 6 items requested
Awaiting
PS
Priya S.
OAuth connected · GitHub + Claude Code + Cursor
Auto-ingesting
HN
Haseeb N.
OAuth connected · Sales lane, GitHub only
Auto-ingesting
4
First three-way agreement approval
Manager approves the first AI-proposed hours → engineer signs → task can move to "In progress"
Waits on step 3
  • What happens automatically once step 3 completes for at least one engineer:
  1. Engineer creates or moves a task to In progress
  2. AI Helper proposes hours (real Claude API · uses your AI Helper profile from step 1 + past similar tasks)
  3. Engineer signs (accepts the AI number, or counters with their own + one-line reason)
  4. Manager approves — dashboard button, or one-click Zoom / Slack reply · takes ~30 seconds
  5. Task moves to In progress; hours locked for delta scoring
Try it with sample tasks
Creates a team + 3 tasks (2 approved with actuals, 1 awaiting approval) so Steps 4 and 5 have data to show without waiting for a real commit.
Without manager approval, the task can't advance — the API returns HTTP 409 three_way_agreement_required. This is the intentional gate that makes the KPI fair (no post-hoc goalpost moving).
5
First weekly reprot generates
Diary-rollup cron computes the numbers · Monday morning of week 2, your team's real KPI is live
7 days after step 3
  • Nightly: 23:15 UTC · daily rollup per engineer → diary_rollups (period_type=day)
  • Weekly: Sunday 23:45 UTC · aggregates the week → diary_rollups (period_type=week)
  • Monthly: 1st of month 00:00 UTC → diary_rollups (period_type=month)

On Monday morning of week 2 (7 days after step 3 completes), you can open:

Real-time signals — task board, live activity feed, and cost tracking — are visible from day 1 as soon as step 3 completes for that engineer. Only the aggregated weekly delta scores need the 7-day window to be statistically meaningful.

Data ownership: everything R&D Workforce collects is yours · one-click CSV/JSON export from any dashboard page · GET /api/wf/export?subscriber_id=<yours>&format=json for full-fidelity API export · cancellation retains 30 days then hard-deletes (per Terms). See submission spec · Connect flow · AI Helper config.