Festive storefront
Storefront build · Due 24 Oct
On trackBuild study · Our own productResurgam Digital
WorkBoard
The operations platform we built to run Resurgam, with Claude in the loop.
- Launched
- September 2026
work.resurgam.digital
Portfolio
Sample dataSearch visibility retainer
SEO · Monthly
At riskBrand refresh
Branding · Due 12 Nov
Off trackNew draft from Claude: 4 phases, 23 tasks, 3 milestones, 4 goals
Review and publish- Client
- Resurgam Digital
- Industry
- Agency Operations
- Technology
- Express, Google sign-in, Hostinger Cloud, Model Context Protocol, MySQL, Node.js 22, OAuth 2.1, React 18, TypeScript, Vite
Overview
Built for how we work
When Resurgam hired its first full-time developer on a hybrid schedule, we needed a clear view of who was doing what, how each project was really going and where time was going. The off-the-shelf tools we tried charged per seat, came padded with features we’d never use, and couldn’t answer the question we cared about most: is this project late, and whose fault is it really?
So we built our own. WorkBoard runs on hosting we already paid for, knows how an agency delivers work, and connects to Claude so planning, monitoring and reporting take minutes. A person still approves everything before the team sees it.
Measurable impact
What changed
Measuring now · figures publish after 90 days in use
—Tasks delivered on time
Share of tasks finished by their due date, with client and scope delays excused.
—Time to plan a new project
From brief to a phased plan with tasks, dependencies and milestones. Before vs after.
—Hours a week saved on status updates
Time the founder spent chasing updates over calls and WhatsApp.
—Daily log consistency
Working days with a daily log across the team.
—Time to produce a client report
From request to a branded report built from live project data.
—Yearly subscription cost avoided
Compared with per-seat project tools at our team size.
Challenges and solutions
What we had to solve
Seven operational problems shaped the platform and its safeguards.
Challenge
Project tools charge per seat
Per-seat pricing grows with every hire, and the features we’d actually use sat in the higher plans.
Solution
Self-hosted, without per-seat fees
A self-hosted platform on the cloud hosting we already run. No per-seat fees, and every project, task and log stays in our own database.
- Runs on its own subdomain and database, separate from client sites
- One-click backup export for safekeeping in Google Drive
Challenge
Project status was scattered
Updates lived in WhatsApp groups, calls and memory. There was no single place to see which projects were slipping.
Solution
Project health is calculated
Every project has phases, milestones and tasks with dependencies, in table, Kanban and timeline views. Health is calculated, not guessed.
- On track, at risk or off track from overdue and stuck tasks and calendar progress
- Needs-attention dashboard banner
- Staging and demo links with preview
Challenge
Late work was blamed on the wrong person
A task that’s late because the client didn’t send content looks the same as one that’s late because it was underestimated.
Solution
A fair delivery score
When a task finishes late, WorkBoard asks why. Client, teammate and scope-change delays do not count against the owner.
- On-time delivery, estimate accuracy, review passes and daily logs
- No score until enough tasks are complete
- Scores do not apply to founders
Challenge
Keeping track of hybrid work
With two work-from-home days a week, we needed a record of the work without micromanaging.
Solution
A two-minute daily log
Done, next and blockers are linked to real tasks, with an activity feed across every project.
- Missed logs flagged on working days
- Google Workspace sign-in with no new passwords
Challenge
Planning took hours of the founder’s time
Turning a client brief into phases, tasks, estimates and dependencies was slow, and the method lived in one person’s head.
Solution
Claude drafts from live context
A Model Context Protocol connector lets Claude read the portfolio, draft project plans and goals, and build reports from live numbers.
- Draft phases, tasks, milestones and goals
- Past projects become templates
- Ask what needs attention today using real data
Challenge
AI had to be safe to trust
An assistant that could change live work, or that the whole team could reach, would be a risk.
Solution
Read and draft, never publish
Claude can read and draft, but it cannot publish. Only an admin can connect it, and every plan waits for human approval.
- OAuth 2.1 with PKCE and hashed short-lived tokens
- No tool can publish or change tasks, people or settings
Challenge
Client reports took too long
Weekly updates meant pulling numbers from several places and formatting them by hand.
Solution
Reports from live project data
Claude writes the narrative and WorkBoard prints a branded PDF from current delivery data.
- Separate client and internal versions
- Client reports omit hours and individual performance
How Claude fits in
05 — 10Human in the loop
A person approves every step
Claude prepares the work from live project context. WorkBoard holds it as a draft until a person decides to publish.
- 01Founder
Shares the brief
Scope, deadline and constraints, in plain language.
- 02Claude
Drafts the plan
Phases, tasks, estimates, dependencies, milestones and goals.
- 03WorkBoard
Holds it as a draft
Checked for missing links and dependency loops. The team can’t see it yet.
- 04Founder
Reviews and publishes
Edits anything, then publishes in one action.
- 05Team
Gets to work
Owners are assigned and dates go live on the timeline.
Claude prepares; a person decides.
The same pattern covers project goals and client reports.Process
Design first, then build in phases
- Step 1 · Done
Design and approval
Features, screens and tech stack agreed before any code was written.
- Phase 1 · Live
Delivery core
Projects, tasks, dependencies, timeline, daily logs, dashboards, team performance and Google sign-in.
- Phase 2 · Live
Claude connector
Drafts with approval, project goals, templates, the report builder and a secure connector.
- Phase 3 · Next
Growth and mobile
Role-based access, retainers, sales pipeline, scope approvals, Google Workspace, n8n and an iPhone app.
Under the hood
Technology
A lean TypeScript stack, chosen to run reliably next to live client websites on shared cloud hosting. It uses little memory and shows a clear diagnostic page instead of crashing.
- Express
- Google sign-in
- Hostinger Cloud
- Model Context Protocol
- MySQL
- Node.js 22
- OAuth 2.1
- React 18
- TypeScript
- Vite
- 125
- Automated checks run before every release
- 15
- Claude tools covering monitoring, planning and reports
- 0
- Per-seat fees, at any team size