Opportunities › All-in-one PSA platform for managed service providers › Proposed app
Tillbook
One workspace for tickets, assets, licenses, billing and docs at small MSPs
- Score
- 52
- confidence 35
- Evidence
- 1
- items on the page
- Rivals
- 0
- named in sources
- First version
- 60 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 1996
- Mature market · AI estimate
ScreensConcept
Desktop app: MSP technicians log tickets and time, manage licenses and invoices at a desk, though the phone view is available for brief field checks. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Harbor Dental
Healthy14 assets
About this appAI proposal
Tillbook puts a small managed service provider's daily work in one place: clients, contacts, devices, software licenses, tickets, invoices and documentation. Each client has one page that shows everything you run for them, so technicians stop switching between tools.
It is built for MSPs with a handful to a few dozen technicians who now stitch together separate ticketing, asset, billing and documentation tools and reconcile them by hand. A ticket links to the device, the license and the billable time without re-entering anything.
The market evidence is thin: the material shows one open-source repository gaining 1025 GitHub stars in 2775 days, and names no competitors or prices. Tillbook is a proposal to test, not a proven market.
- Tagline
- The whole MSP desk in one place.
- Voice
- PlainPracticalCalm
- Why this name
- A till is where a day's work is counted, and a book is where it is recorded. Tillbook suggests work logged and billed in one place.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
One page per client
Contacts, sites, assets, licenses, open tickets, contracts and docs on a single client view.
No member yet
Tickets linked to assets
Attach a device or license to a ticket. History follows the asset, not just the person who asked.
No member yet
Time to invoice
Ticket time and recurring services roll into draft invoices per client, ready to review and send.
No member yet
License tracker
Seats bought, seats used and renewal dates per client, with alerts before a renewal is missed.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C5CDeep Teal · primary#F7F4ECPaper · surface#1D2A2EInk · text#E09F3EAmber · accent#5E8C61Moss · data / success
Typography
Aa
Tillbook
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
The whole MSP desk in one place.
PricingAI proposal
The material gives no competitor prices. These per-technician tiers follow the monetization idea in the source and are a starting point to test.
Starter
Free
- 1 technician
- Up to 5 clients
- Tickets, assets, docs
Team
$29 a month
- Per technician
- Unlimited clients and assets
- Billing and license tracking
- CSV import
Growth
$49 a month
- Per technician
- Everything in Team
- Contract templates
- Audit log and roles
Would you pay Team · $29 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Clients receive invoices, ticket updates and a client portal link branded with a small Tillbook footer. Their technicians' reports and invoices carry it to the MSP's customers.
- Do they become customers?
- Clients of an MSP are rarely buyers of PSA software, so exposure may bring little. Test whether any client contacts who run IT elsewhere ask about the footer link.
- First customers
- MSPs with 2 to 10 technicians serving small local businesses, whose owner still handles billing and tool setup personally.
- Where to reach them
- MSP communities: Join owner forums and chat groups, ask about tool sprawl, offer free migration help to a few shops.
- Direct outreach: Email small local MSP owners with a short demo of one client page and ticket-to-invoice flow.
- Open-source users: Reach people starring or discussing open-source PSA tools and offer a hosted alternative.
- First milestone
- Five small MSPs paying for Team seats after a 30-day trial, each running live tickets and one billing cycle.
Why people already pay for this
- VerifiedGitHub repository gained 1025 stars in 2775 days
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Background jobsScheduled job runnerRecurring invoices and renewal alerts need reliable timed tasks.
- This app · PDF generationServer-side PDF renderingInvoices and client reports must be sent as documents.
RisksAI inference
- CommercialThe evidence is one repository's star growth. Demand and willingness to pay among small MSPs is unproven, and switching away from existing tools is costly.
- CommercialAll-in-one scope is wide. A first version may be too shallow in each area to replace specialist tools.
- TechnicalWithout integrations for remote monitoring and accounting tools, assets and invoices need manual entry, weakening the value.
- DataStores client credentials-adjacent documentation and device data. A breach would be severe, so access control and audit logs are needed early.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.