Example package
Online booking
A booking page with your services, staff and availability, on your website.
You get
- Services, durations and buffers set up
- Staff availability and calendar sync
- Booking page embedded on your site
- Confirmation emails
Sound familiar?
What we hear from businesses before a project like this starts.
- Half our day is back-and-forth emails to find a time.
- No-shows cost us a slot every day, and nobody follows up.
- The booking tool doesn't know about our staff rota, so we get double-booked.
- Bookings, payments and the customer list live in three places that never match.
- We need deposits for some services and not others.
What buyers usually need
The requests that come up most often for this kind of work, and what each one takes to work properly.
01
Customers book themselves
A booking page with your services, staff and real availability, on your website and your Google profile.
02
Reminders that cut no-shows
Email and text reminders, a confirm link, and a re-booking message when someone misses.
03
Staff, rooms and buffers
Rules for who can do what, travel or clean-up time between jobs, and no double-booking.
04
Deposits and payments
A deposit or full payment at booking where you want it, with cancellation rules.
05
Bookings in the CRM
Each booking creates or updates the customer record and the deal, with the source.
06
A daily view for the team
Tomorrow's schedule by staff member, sent each evening or shown on one screen.
Tools that come up most: Calendly, Acuity, Square Appointments, SimplyBook, Cal.com, Google Calendar, Outlook, Stripe, Twilio, HubSpot and GoHighLevel.
What you get
Concrete pieces, each one something you can open and check when it's done.
Booking page
Services, staff and real availability, embedded on your site.
Calendly, Acuity, Cal.com, custom pageReminders and confirmations
Email and text reminders with confirm and reschedule links.
Email, SMS, TwilioNo-show recovery
A re-booking message and a task when someone misses.
Workflows, webhooksDeposits
Payment at booking with cancellation rules.
Stripe, SquareCRM and calendar sync
Bookings create the customer and deal, and block staff calendars.
HubSpot, GoHighLevel, Google CalendarDaily schedule
Tomorrow's bookings by staff member, every evening.
Email digest, Google SheetsTypical projects
Example packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Reminders and no-show recovery
Fewer missed appointments, and a follow-up when one happens.
You get
- Email and text reminders
- Confirm and reschedule links
- No-show re-booking message
- A test log of each path
Example package
Booking with deposits
Payment or a deposit taken at booking, with your cancellation rules.
You get
- Deposit rules per service
- Stripe or Square connected
- Cancellation and refund rules
- Payment status on each booking
Example package
Booking connected to everything
Bookings flow into your CRM, calendars and a daily schedule for the team.
You get
- Customer and deal created on booking
- Staff calendars blocked
- Evening schedule email per staff member
- Notes on how to change services and hours
How we approach it
The habits that keep this kind of project from going wrong.
1
Start from the rota
We write down who does what, when and where before choosing settings, so the calendar matches reality.
2
Use the tool you have
If your booking tool can do the job, we configure it properly rather than replacing it.
3
Test every path
Book, reschedule, cancel, miss, pay and refund are each tested with test bookings. You get the log.
4
Messages that deliver
Texting is checked for registration and sending limits before reminders go live.
How we work
You know what you're getting before work begins, and you see it working at every milestone.
You describe it
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
A written scope
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
Milestones you review
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
Handover and a 30-day fix window
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
What shapes the scope
- How many services, staff and locations
- Whether bookings take payment
- Which calendar and CRM it connects to
- Whether you need a custom booking page
Always included
- A written scope before work starts
- Milestones you review and sign off
- Documentation and a walkthrough at handover
- A 30-day window for fixes, at no charge
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
Questions people ask first
Do we have to change booking tools?
No. Most of the time we set up the tool you already have. We only suggest a switch when it can't do something you need, and say so in the scope.
Can reminders go by text?
Yes. US business texting needs carrier registration; we tell you in the scope whether yours is done and prepare it with you, but approval is decided by the carriers.
Can customers pay when they book?
Yes, through Stripe or Square, with deposit and cancellation rules you choose.
What if we want changes halfway through?
Small adjustments inside the agreed scope are included. Anything new gets its own short written scope, and we only do it if you approve it.
What happens after handover?
For 30 days we fix anything we built that does not work as the scope describes, at no charge. After that, further work is scoped the same way.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com