Demo
Trial / demo
€0
✓
1 WBSO project
✓
3 users
✓
25 hour entries
✓
25 evidence items
// scatter
The hidden problem
WBSO usually goes wrong after the work is done.
The technical work happens across the tools your team already uses — code, issues, docs, meetings, and code reviews. The administration often has to be reconstructed later.
- Hours fall behindDevelopers log hours late, incomplete, or not per WBSO project.
- Evidence is fragmentedTechnical progress lives across the tools your team already uses — code, issues, documents, notes, and internal discussions.
- Review stress comes lateFinance, founders, or advisors need to reconstruct what was built, when, by whom, and why it mattered.
// snap into place
Turning point
R&Dossier connects the pieces.
Create WBSO projects, assign members, register hours, automatically sync technical work from the systems your team already uses, link evidence to hours, and export a structured auditpack when you need it.
Not another spreadsheet. A workflow for keeping your WBSO dossier alive during the year.
// the workflow
How it works
A guided walk through your WBSO workflow.
Create the project, connect your tools, review what syncs in, turn it into hours and evidence, link them, and export — each step a point on the same structured dossier.
Projects
Create your WBSO project
Define the technical description, approved hours, and development period for each R&D track.
$ project: adaptive-retrieval · 1,600h approved · Jan–Jun 2026Integrations
Connect the tools you already use
Map your development tools and time tracker to your WBSO projects so the relevant work syncs in automatically — no change to how your team works.
Optional — you can also work entirely by hand.
$ mapped: org/retrieval-api → adaptive-retrieval · synced: 14 itemsCandidates
Review what synced in
Synced work lands as candidates first — evidence candidates from your dev tools, hours candidates from your time tracker. Your team decides what belongs in the dossier.
Switch on auto-import and this review step happens on its own.
$ scanned: 14 candidates · 9 evidence · 5 hours · awaiting reviewEvidence & hours
Import evidence and hours
Approved candidates become evidence and draft hours against the project, ready to review and confirm.
Or add evidence and log hours by hand — no integration required.
$ imported: 6 evidence · 12h draft · +2 manual notesLink
Link evidence to hours
Connect each piece of evidence to the hours it supports, so work, people, and technical progress explain each other.
Auto-link can make the confident matches for you.
$ linked: PR #1421 → 3 hour entriesExport
Export the auditpack
Generate a structured WBSO auditpack with projects, hours, evidence, evidence-hour links, and attention points.
$ export: wbso-auditpack-2026.xlsx · projects · hours · evidence · links// tributaries merge
Integrations
The integrations are the point.
Your team keeps working in the tools they already use — nothing changes in their workflow. R&Dossier connects to those systems and syncs the relevant work automatically: development tools become review-ready WBSO evidence, and your time tracker becomes registered hours.
- Sync new work from your toolsR&Dossier
- Decide what counts as evidenceYou — or automatic
- Link evidence to the hours it supportsYou — or automatic
- Export the auditpackYou
Missing an integration? We co-invest in new connectors →
// hands off the rail
Automation
Then hand over the parts that don’t need you.
You have just seen the whole walk. Most of it can run without you — but only the parts where a machine cannot get it wrong in a way an auditor would notice. R&Dossier automates collection, not judgement.
- Always automaticScanning your connected tools for new activity. It only fills a review queue — nothing about a scan reaches your dossier.
- Automatic if you say soTurning synced work into evidence, turning synced time into draft hours, and linking evidence to the hours it supports. Each runs daily, every weekday, or weekly — your choice.
- Never automaticConfirming hours, submitting or approving a project, or deciding that an uncertain match is real. Those stay with your team.
Every automation is off until you switch it on, runs on the schedule you set, and can be undone — and each action it takes is written to an automation log you can audit, so the parts that run on their own are never a black box.
A living WBSO dossier.
Built during the year — not reconstructed at the deadline.