[{"data":1,"prerenderedAt":325},["ShallowReactive",2],{"service-membership":3,"service-membership-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\u002Fmembership.md","Membership and subscriptions",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"what-a-starter-membership-product-looks-like","What a starter membership product looks like",[15,16,17],"p",{},"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,19,21],{"id":20},"where-the-build-scales","Where the build scales",[15,23,24],{},"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,26,28],{"id":27},"what-we-will-not-build","What we will not build",[15,30,31],{},"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":35},"",2,[36,37,38],{"id":12,"depth":34,"text":13},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"md","MEMBERSHIP AND SUBSCRIPTION PRODUCTS",[42,45,48,51],{"q":43,"a":44},"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":46,"a":47},"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":49,"a":50},"Sales tax?","Stripe Tax handles US sales tax and EU VAT. We wire it up at the floor.",{"q":52,"a":53},"How long until launch?","Six to ten weeks at the $30k floor. Stripe wiring is the biggest variable.","$30k","Recurring revenue, gated correctly.",[57,58,59,60,61,62],"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",{},true,100,"\u002Fservices\u002Fmembership",[68,71,74,77],{"title":69,"body":70},"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":72,"body":73},"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":75,"body":76},"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":79},"Owned by you","Code, Stripe, email tool, customer data all in your accounts. Memberships are too operational to depend on a vendor.","Phase-by-phase quote, fixed bid",[82,83],"saas","ecommerce",[85,86,87,88,89],"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":5,"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","membership",[95,98,101,104,107],{"name":96,"note":97},"Nuxt or Next + Postgres","Multi-tenant subscription data model.",{"name":99,"note":100},"Stripe Billing + Tax","Proration, dunning, customer portal, sales tax.",{"name":102,"note":103},"Klaviyo \u002F Customer.io","Lifecycle email wired to real events.",{"name":105,"note":106},"PostHog \u002F Amplitude","Churn cohorts, MRR, expansion tracking.",{"name":108,"note":109},"Inngest","Webhook handling, scheduled jobs (renewal reminders).","services\u002Fmembership","Subscription products with Stripe Billing, gated content, customer portals, churn-aware lifecycle email.","second","aTM0XDAWjZBOdOTytgPi_EK80zElleAF1MC8n3tqGlo",[115,221],{"id":116,"title":117,"body":118,"description":33,"extension":39,"eyebrow":142,"faq":143,"fromPrice":162,"headline":163,"includes":164,"meta":171,"navigation":64,"order":172,"path":173,"pillars":174,"priceNote":80,"related":186,"scales":189,"seo":195,"seoDescription":196,"seoTitle":197,"slug":82,"stack":198,"stem":217,"subhead":218,"tier":219,"__hash__":220},"services\u002Fservices\u002Fsaas.md","SaaS \u002F web app",{"type":7,"value":119,"toc":137},[120,124,127,129,132,134],[10,121,123],{"id":122},"what-a-starter-saas-build-looks-like","What a starter SaaS build looks like",[15,125,126],{},"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,128,21],{"id":20},[15,130,131],{},"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,133,28],{"id":27},[15,135,136],{},"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":138},[139,140,141],{"id":122,"depth":34,"text":123},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"SAAS DEVELOPMENT",[144,147,150,153,156,159],{"q":145,"a":146},"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":148,"a":149},"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":151,"a":152},"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":154,"a":155},"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":157,"a":158},"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":160,"a":161},"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.",[165,166,167,168,169,170],"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",[175,178,181,184],{"title":176,"body":177},"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":179,"body":180},"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":182,"body":183},"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":185},"Schema, migrations, deploy keys, observability. All in your accounts. We work for you, the code does too.",[187,188],"ai-integrations","internal-tool",[190,191,192,193,194],"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":117,"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",[199,202,205,208,211,214],{"name":200,"note":201},"Nuxt 3 or Next.js","SSR-first. Choice depends on your stack and your team.",{"name":203,"note":204},"TypeScript strict","Types derived from schema, no any escapes.",{"name":206,"note":207},"Drizzle or Prisma + Postgres","Migrations checked in, no manual schema drift.",{"name":209,"note":210},"NextAuth \u002F Clerk \u002F Better Auth","Multi-tenant patterns from day one.",{"name":212,"note":213},"Stripe Billing","Subscriptions, metered usage, customer portal.",{"name":215,"note":216},"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",{"id":222,"title":223,"body":224,"description":33,"extension":39,"eyebrow":248,"faq":249,"fromPrice":268,"headline":269,"includes":270,"meta":277,"navigation":64,"order":278,"path":279,"pillars":280,"priceNote":80,"related":292,"scales":294,"seo":300,"seoDescription":301,"seoTitle":302,"slug":83,"stack":303,"stem":322,"subhead":323,"tier":219,"__hash__":324},"services\u002Fservices\u002Fecommerce.md","Ecommerce",{"type":7,"value":225,"toc":243},[226,230,233,235,238,240],[10,227,229],{"id":228},"what-a-starter-ecommerce-build-looks-like","What a starter ecommerce build looks like",[15,231,232],{},"The $40k floor covers a headless storefront on your platform of record, up to 20 templated pages, the full PDP\u002FPLP\u002Fcart\u002Fcheckout flow, Klaviyo wired up, and pixel events on every funnel step. Six to ten weeks typical.",[10,234,21],{"id":20},[15,236,237],{},"Multi-region commerce is the most common scaler. Localized currency, localized fulfillment, and localized SEO each have their own cost. B2B is next: account approvals, NET 30 terms, and custom pricing rails change the data model. Subscriptions and bundles change checkout. Each of these is a real chapter of work, not a checkbox.",[10,239,28],{"id":27},[15,241,242],{},"Stores on theme platforms when you've already outgrown the theme. Stores with no analytics. Anything where the back-of-store changes faster than the front-of-store can keep up.",{"title":33,"searchDepth":34,"depth":34,"links":244},[245,246,247],{"id":228,"depth":34,"text":229},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"CUSTOM ECOMMERCE",[250,253,256,259,262,265],{"q":251,"a":252},"Why headless instead of a theme?","Themes optimize for setup speed. Headless optimizes for the speed your customer feels and the freedom to ship anything. For a brand doing real volume the theme tax compounds, and we are usually rebuilding because that tax came due.",{"q":254,"a":255},"Do you do Shopify Plus?","Yes. We work with the Plus partner network for Launchpad, Scripts, Functions, and Flow. We are not a Plus partner in the official-list sense but we have shipped against Plus several times.",{"q":257,"a":258},"How do you handle SEO during migration?","A 301 plan written before launch. We pull every indexed URL from Search Console, map each to its new path, and ship the redirect map with the codebase.",{"q":260,"a":261},"Can we use our existing design?","Yes if it works. If it does not work we will tell you, and offer a design phase. We don't ship work we wouldn't put on our own portfolio.",{"q":263,"a":264},"What hosts do you support?","Vercel is the default. Cloudflare Pages and Workers for edge-heavy work. We can deploy to your own AWS or GCP if you require it.",{"q":266,"a":267},"How is this different from agencies that resell templates?","Every line is ours. There's no theme to fight with, no plugin that mysteriously breaks on update, no upsell to a \"premium\" tier of features that are just code. The codebase is the deliverable.","$40k","Storefronts that load in under a second.",[271,272,273,274,275,276],"Headless storefront on Shopify, BigCommerce, or custom","Up to 20 templated pages plus PDP\u002FPLP\u002Fcart\u002Fcheckout","Klaviyo flows wired (welcome, abandoned cart, post-purchase)","Meta Pixel and Klaviyo events on every funnel step","Core Web Vitals report at launch and 30-day check","Two-week post-launch support window",{},20,"\u002Fservices\u002Fecommerce",[281,284,287,290],{"title":282,"body":283},"Sub-second LCP on real catalogs","We measure the page that matters, not the homepage. Product list and PDP both ship under a second on real device traces.",{"title":285,"body":286},"Conversion hypothesis per release","Every milestone ties to a metric. Faster checkout. Higher add-to-cart. Lower bounce on PDP. We tell you what moved and what didn't.",{"title":288,"body":289},"Keep your back office","Shopify, BigCommerce, or your custom stack stays. We build the front-end that talks to it without paying the theme tax on every render.",{"title":78,"body":291},"Codebase, hosting, analytics, accounts. All transferred at launch. You ship the next change without us if you want to.",[82,293],"marketing-site",[295,296,297,298,299],"Multi-region storefronts with localized currency and fulfillment","B2B layers (account approvals, NET 30, custom pricing)","Custom checkout (Shop Pay extensions, additional payment rails)","Subscription, bundles, gift-card mechanics","Multi-warehouse routing and IMS integrations",{"title":223,"description":33},"Custom-coded ecommerce storefronts. Headless Shopify, BigCommerce, or custom commerce. Sub-second loads, conversion-tuned design, owned by you. Starting at $40k.","Custom Ecommerce Development | Headless Shopify and BigCommerce | HARTECHO",[304,307,310,313,316,319],{"name":305,"note":306},"Nuxt \u002F Next.js","SSR-first for SEO, hand-tuned per route.",{"name":308,"note":309},"Shopify Hydrogen or Storefront API","When Shopify is the source of truth.",{"name":311,"note":312},"BigCommerce Catalyst \u002F API","When BigCommerce is.",{"name":314,"note":315},"Klaviyo, Postmark, ShipStation","The post-checkout pipeline most stores need wired in.",{"name":317,"note":318},"Vercel \u002F Cloudflare","Edge runtime where it earns the cost.",{"name":320,"note":321},"Datadog \u002F Sentry \u002F CrUX","Real-user metrics, not synthetic.","services\u002Fecommerce","Headless on Shopify, BigCommerce, or a custom stack. Hand-coded, conversion-tuned, measured in real Core Web Vitals. Built for brands that have outgrown their theme.","CJIOvnLDJ00w1YQtnpjcR47I0OyrsmEW_qtiaLsy3NA",1779549900437]