Sample build plan
What you get before you pay for a build.
Every engagement starts with a one-week discovery that ends in this document. The product below is illustrative. The structure, the trades, and the terms are exactly what a client signs.
Build plan
Shiftly
Fixed price
Shift scheduling for independent restaurants, replacing the WhatsApp group and the spreadsheet.
A two-founder team, one with ten years running restaurants.
Thesis
Managers will move scheduling off WhatsApp if publishing a week's rota takes under five minutes and staff can swap shifts without the manager in the loop.
v1 must prove
Three restaurants publish four consecutive weekly rotas in the product and at least half of shift swaps happen without manager involvement.
Fixed scope
Accounts
- -Manager sign-up and restaurant setup
- -Staff invite by SMS link, no password
- -Roles: owner, manager, staff
Rota builder
- -Weekly grid, drag to assign, copy last week
- -Availability and time-off requests
- -Publish with SMS notification to staff
Shift swaps
- -Staff offer a shift, eligible colleagues accept
- -Auto-approve within rules, manager override
- -Audit trail per shift
Reporting
- -Hours per person per week
- -Labour cost against a weekly target
- -CSV export for payroll
Platform
- -Responsive web app, installable on phones
- -SMS via Twilio, email via Resend
- -Error tracking, analytics, backups
Pushed to v2
Native iOS and Android apps
The installable web app proves whether staff open it. Native follows when retention says so.
Payroll integrations
CSV covers the first ten restaurants. Each integration is its own project.
Multi-location management
Single-site first. Groups are a different buyer with different needs.
Forecasting from sales data
Needs POS integrations and months of data. v3 at the earliest.
Timeline
- Week 1DiscoverThis document. Interviews with four restaurant managers. Stack and architecture decision.
- Week 2 to 3DesignFlows for publish and swap. Clickable prototype tested with three managers. Design system.
- Week 4BuildAccounts, restaurant setup, staff invites. Staging live, continuous deployment.
- Week 5 to 6BuildRota builder and publish flow. First Friday demo with a real rota.
- Week 7 to 8BuildShift swaps and rules engine. Reporting and export.
- Week 9BuildPolish, edge cases, security pass, load test on publish.
- Week 10LaunchProduction, monitoring, onboarding the three pilot restaurants by hand.
Team and cadence
- -Product designer, weeks 2 to 4 full-time, then on call
- -Technical lead, full engagement
- -Two senior engineers, weeks 4 to 10
- -Founder time: one 45-minute demo per week plus async review
Demos: Every Friday at 14:00, on staging, with a written summary the same day.
Terms
- -Fixed price for the scope above, agreed before week 2 starts.
- -Payment in three parts: on signature, at the end of week 5, at launch.
- -Scope changes are trades: something comes in, something of equal size moves to v2.
- -All code in the client's repositories from day one. Full ownership on final payment.
- -Two weeks of post-launch fixes included.
Contact
Have a project in mind?
We reply within 24 hours.