[{"data":1,"prerenderedAt":313},["ShallowReactive",2],{"service-booking":3,"service-booking-related":114},{"id":4,"title":5,"body":6,"description":33,"extension":39,"eyebrow":40,"faq":41,"fromPrice":54,"headline":55,"includes":56,"meta":63,"navigation":64,"order":65,"path":66,"pillars":67,"priceNote":80,"related":81,"scales":84,"seo":90,"seoDescription":91,"seoTitle":92,"slug":93,"stack":94,"stem":110,"subhead":111,"tier":112,"__hash__":113},"services\u002Fservices\u002Fbooking.md","Booking platforms",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"what-a-starter-booking-platform-looks-like","What a starter booking platform looks like",[15,16,17],"p",{},"Multi-resource availability, customer booking flow, Stripe deposits, reminders, calendar sync, admin. Eight to twelve weeks. The booking and no-show flows both work end-to-end at launch.",[10,19,21],{"id":20},"where-the-build-scales","Where the build scales",[15,23,24],{},"Multi-location is the most common scaler (location-specific availability, pricing, staff rules). Group bookings need their own data model. Class-pass and inventory mechanics add a usage layer on top of the booking core.",[10,26,28],{"id":27},"what-we-will-not-build","What we will not build",[15,30,31],{},"Booking platforms with no deposit flow (the no-show problem will eat you). Anything where the customer cannot see live availability.",{"title":33,"searchDepth":34,"depth":34,"links":35},"",2,[36,37,38],{"id":12,"depth":34,"text":13},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"md","BOOKING AND SCHEDULING",[42,45,48,51],{"q":43,"a":44},"Why not Calendly or Acuity?","They are great for simple cases. The moment you have multi-resource booking, custom pricing rules, deposits with tiered refunds, or branded checkout, the off-the-shelf tools start to leak. We rebuild from them often.",{"q":46,"a":47},"How long until launch?","Eight to twelve weeks at the $35k floor. The hard work is rules, not screens.",{"q":49,"a":50},"What about timezone bugs?","We test DST transitions and edge cases as part of QA. Storing UTC and rendering in the user's zone is the discipline. We do not get this wrong.",{"q":52,"a":53},"Can it text customers reminders?","Yes, via Twilio. 24-hour and 1-hour reminders by default. Configurable per service.","$35k","Bookings that don't double-book.",[57,58,59,60,61,62],"Multi-resource availability model (staff, rooms, equipment)","Customer-facing booking flow with calendar pick","Stripe deposit collection (auth-hold or charge-now)","Email and SMS reminders at 24h and 1h","Google Calendar two-way sync for one provider","Admin to see and override bookings",{},true,90,"\u002Fservices\u002Fbooking",[68,71,74,77],{"title":69,"body":70},"Timezone math that actually works","We store UTC, render in the user's zone, and test against DST transitions. The bug that loses three customers a year never ships.",{"title":72,"body":73},"Deposits via Stripe","Auth-hold or charge-now, with refund rules per service. The no-show flow is built, not bolted on.",{"title":75,"body":76},"Calendar sync","Google Calendar and iCal at the floor. Outlook on request. Two-way sync so the provider never double-books.",{"title":78,"body":79},"Owned by you","Code, Stripe account, calendar credentials, hosting. The booking flow is mission-critical, you should own all of it.","Phase-by-phase quote, fixed bid",[82,83],"membership","saas",[85,86,87,88,89],"Multi-location with location-specific rules","Group bookings, packages, gift cards","Loyalty or membership pricing tiers","Customer mobile app (see Mobile)","Inventory or class-pass mechanics",{"title":5,"description":33},"Custom booking and scheduling platform development. Availability rules, deposits via Stripe, reminders, calendar sync, no-show handling. Starting at $35k.","Booking Platform Development | Custom Scheduling and Reservation Software | HARTECHO","booking",[95,98,101,104,107],{"name":96,"note":97},"Nuxt or Next + Postgres","With Luxon or date-fns-tz for timezone math.",{"name":99,"note":100},"Stripe (or PaymentIntents)","Deposits, no-show charges, refund rules.",{"name":102,"note":103},"Google Calendar API \u002F Microsoft Graph","Two-way sync per provider.",{"name":105,"note":106},"Twilio + Postmark","Reminders and confirmations.",{"name":108,"note":109},"Inngest","Reminder scheduling, no-show enforcement.","services\u002Fbooking","Scheduling, availability rules, deposits, reminders, no-show flows. Built against real calendar systems with real timezone math.","second","M_2TMDL1fYiGC1I2csRKw8WkyYcH8ztM2PUMy9dtJow",[115,207],{"id":116,"title":117,"body":118,"description":33,"extension":39,"eyebrow":142,"faq":143,"fromPrice":155,"headline":156,"includes":157,"meta":164,"navigation":64,"order":165,"path":166,"pillars":167,"priceNote":80,"related":179,"scales":181,"seo":187,"seoDescription":188,"seoTitle":189,"slug":82,"stack":190,"stem":204,"subhead":205,"tier":112,"__hash__":206},"services\u002Fservices\u002Fmembership.md","Membership and subscriptions",{"type":7,"value":119,"toc":137},[120,124,127,129,132,134],[10,121,123],{"id":122},"what-a-starter-membership-product-looks-like","What a starter membership product looks like",[15,125,126],{},"One to three tiers, gated content, Stripe Billing with portal, lifecycle email, webhook handler, churn dashboard. Six to ten weeks. The full subscription lifecycle works at launch.",[10,128,21],{"id":20},[15,130,131],{},"Team accounts (multiple users sharing one subscription) are the most common scaler. Trials with credit card collection, freemium with usage-based upgrade triggers, and seat-based billing each have their own data model. Affiliate programs add their own attribution and payout layer.",[10,133,28],{"id":27},[15,135,136],{},"Memberships with no real recurring value. Memberships where the founder has not yet validated anyone will pay for the second month.",{"title":33,"searchDepth":34,"depth":34,"links":138},[139,140,141],{"id":122,"depth":34,"text":123},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"MEMBERSHIP AND SUBSCRIPTION PRODUCTS",[144,147,150,153],{"q":145,"a":146},"Should we use Memberstack or Outseta?","For very simple cases yes. The moment you have non-standard pricing rules, multi-tier upgrade paths, or a need to grandfather existing customers, the off-the-shelf tools become the bottleneck. We rebuild from them often.",{"q":148,"a":149},"What about dunning?","Stripe handles the retry schedule. We handle the in-app banner, the lifecycle email, and the eventual restriction of access. All three live in the codebase.",{"q":151,"a":152},"Sales tax?","Stripe Tax handles US sales tax and EU VAT. We wire it up at the floor.",{"q":46,"a":154},"Six to ten weeks at the $30k floor. Stripe wiring is the biggest variable.","$30k","Recurring revenue, gated correctly.",[158,159,160,161,162,163],"One to three subscription tiers with Stripe Billing","Gated content at the route or component level","Customer portal (Stripe-hosted or custom)","Lifecycle email sequence (5 emails)","Webhook handler with retry and dead-letter queue","Churn dashboard in admin",{},100,"\u002Fservices\u002Fmembership",[168,171,174,177],{"title":169,"body":170},"Stripe Billing, properly","Subscriptions, proration, dunning, customer portal, tax. Tested against the failure cases so you don't lose revenue to a webhook race condition.",{"title":172,"body":173},"Gating that scales","Content gated at the route or component level, with role and tier awareness. Free preview vs paid full vs grandfathered all handled.",{"title":175,"body":176},"Lifecycle email built in","Welcome, day-3 check, retention, dunning, win-back. Wired to Klaviyo or Customer.io, all triggered from real events.",{"title":78,"body":178},"Code, Stripe, email tool, customer data all in your accounts. Memberships are too operational to depend on a vendor.",[83,180],"ecommerce",[182,183,184,185,186],"Annual plans with discount and renewal reminders","Trials, freemium, or seat-based pricing","Team \u002F organization accounts (see SaaS)","Bundled physical products (see Ecommerce)","Affiliate or referral program",{"title":117,"description":33},"Custom membership and subscription software. Stripe Billing, gated content, customer portals, dunning. Built against churn metrics from day one. Starting at $30k.","Membership and Subscription Site Development | Stripe Billing and Gated Content | HARTECHO",[191,193,196,199,202],{"name":96,"note":192},"Multi-tenant subscription data model.",{"name":194,"note":195},"Stripe Billing + Tax","Proration, dunning, customer portal, sales tax.",{"name":197,"note":198},"Klaviyo \u002F Customer.io","Lifecycle email wired to real events.",{"name":200,"note":201},"PostHog \u002F Amplitude","Churn cohorts, MRR, expansion tracking.",{"name":108,"note":203},"Webhook handling, scheduled jobs (renewal reminders).","services\u002Fmembership","Subscription products with Stripe Billing, gated content, customer portals, churn-aware lifecycle email.","aTM0XDAWjZBOdOTytgPi_EK80zElleAF1MC8n3tqGlo",{"id":208,"title":209,"body":210,"description":33,"extension":39,"eyebrow":234,"faq":235,"fromPrice":254,"headline":255,"includes":256,"meta":263,"navigation":64,"order":264,"path":265,"pillars":266,"priceNote":80,"related":278,"scales":281,"seo":287,"seoDescription":288,"seoTitle":289,"slug":83,"stack":290,"stem":309,"subhead":310,"tier":311,"__hash__":312},"services\u002Fservices\u002Fsaas.md","SaaS \u002F web app",{"type":7,"value":211,"toc":229},[212,216,219,221,224,226],[10,213,215],{"id":214},"what-a-starter-saas-build-looks-like","What a starter SaaS build looks like",[15,217,218],{},"The $60k floor covers a multi-tenant data model, auth with invites, Stripe billing, an internal admin scaffold, and one core feature loop fully built. Eight to twelve weeks. The point is to land at a working app one user could actually pay for, with the seams in place to grow from there.",[10,220,21],{"id":20},[15,222,223],{},"Multiple feature loops is the most common scaler. Each new loop usually touches the data model, the UI, billing, and admin, so the cost is not linear. Real-time collaboration is a step change in complexity. Public APIs and webhooks add their own contracts to maintain. Enterprise plans (SSO, SCIM, audit) are usually deferred to a separate phase.",[10,225,28],{"id":27},[15,227,228],{},"SaaS that bets the company on a feature no user has asked for. SaaS without billing. Apps where the founder cannot describe the first paying user. Anything where the build is the cheap part and the distribution is unsolved.",{"title":33,"searchDepth":34,"depth":34,"links":230},[231,232,233],{"id":214,"depth":34,"text":215},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"SAAS DEVELOPMENT",[236,239,242,245,248,251],{"q":237,"a":238},"What stage of company is this for?","Founders going from spec to first paying customer, or teams whose v1 was built fast and now needs to actually work. We are not the right shop if you already have ten engineers shipping daily.",{"q":240,"a":241},"How do you split the build from the design?","Discovery and design phases come first. We do not write code against unsolved problems. Once the screens are signed off the build is mostly mechanical.",{"q":243,"a":244},"Can we hand off mid-build?","Yes. Every milestone is a working app. You can stop after design, after the first feature loop, or after launch and we hand off the codebase as-is.",{"q":246,"a":247},"Why Nuxt or Next instead of Rails or Django?","We are faster in TypeScript and the audience usually has TypeScript people on hand for the next hire. We will write Python or Rails for the right project but it is not our default.",{"q":249,"a":250},"How does enterprise stuff fit in?","SSO, SCIM, and audit logs are a real chapter, not a checkbox. We sequence them after product-market fit. Building enterprise-features-first is a common reason for SaaS projects to die.",{"q":252,"a":253},"What about AI in the app?","See AI integrations. Adding LLM features to an existing SaaS is its own scope. We will tell you when AI is the right shape and when it is not.","$60k","Multi-tenant apps, hand-coded.",[257,258,259,260,261,262],"Multi-tenant data model with org + user + roles","Auth (email + OAuth) and team invites","Stripe Billing with one to two plan tiers","Internal admin scaffolding for support and ops","Errors, traces, uptime monitoring at launch","One core feature loop (the thing the app actually does) end-to-end",{},30,"\u002Fservices\u002Fsaas",[267,270,273,276],{"title":268,"body":269},"Real auth, day one","Multi-tenant from the start. Roles, invites, audit trail. NextAuth or Clerk, with the seams in your codebase rather than a black box.",{"title":271,"body":272},"Billing that holds up","Stripe subscriptions, metered usage, proration, dunning. Tested against a real failure-case suite so you don't lose revenue to an edge case.",{"title":274,"body":275},"Admin from sprint one","An internal admin gets built alongside the app, not bolted on after support tickets start. You can see and edit every record in your data.",{"title":78,"body":277},"Schema, migrations, deploy keys, observability. All in your accounts. We work for you, the code does too.",[279,280],"ai-integrations","internal-tool",[282,283,284,285,286],"Multiple feature loops with cross-team workflows","Real-time collaboration (presence, cursors, shared state)","Public API and webhook system for customer integrations","SSO, SCIM, audit logging for enterprise plans","Mobile companion app (see Mobile)",{"title":209,"description":33},"Custom SaaS and web app development. Multi-tenant architecture, Stripe billing, admin dashboards, integrations. Hand-coded in Nuxt or Next, owned by you. Starting at $60k.","Custom SaaS Development | Web App MVP and Beyond | HARTECHO",[291,294,297,300,303,306],{"name":292,"note":293},"Nuxt 3 or Next.js","SSR-first. Choice depends on your stack and your team.",{"name":295,"note":296},"TypeScript strict","Types derived from schema, no any escapes.",{"name":298,"note":299},"Drizzle or Prisma + Postgres","Migrations checked in, no manual schema drift.",{"name":301,"note":302},"NextAuth \u002F Clerk \u002F Better Auth","Multi-tenant patterns from day one.",{"name":304,"note":305},"Stripe Billing","Subscriptions, metered usage, customer portal.",{"name":307,"note":308},"Sentry, Datadog, Better Stack","Errors, traces, uptime. All set up at launch.","services\u002Fsaas","Web applications with real auth, real billing, real admin, real integrations. Built so the second hire on your team can actually read the codebase.","core","t8bDHNs9JzEHooUJw_GA9eJOhLDCTWQazFFWKtCJy-g",1779549900426]