[{"data":1,"prerenderedAt":320},["ShallowReactive",2],{"service-internal-tool":3,"service-internal-tool-related":117},{"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":113,"subhead":114,"tier":115,"__hash__":116},"services\u002Fservices\u002Finternal-tool.md","Internal tool",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"what-a-starter-internal-tool-looks-like","What a starter internal tool looks like",[15,16,17],"p",{},"Six views, role-based access, audit log, one data source, bulk ops with undo, deployed. Six to ten weeks. Built so the ops team feels faster, not slower.",[10,19,21],{"id":20},"where-the-build-scales","Where the build scales",[15,23,24],{},"Multi-source queries are the most common scaler. Workflow engines (approvals, escalations, SLA timers) are their own chapter. Real-time queues with multiple ops users on the same record need careful state design.",[10,26,28],{"id":27},"what-we-will-not-build","What we will not build",[15,30,31],{},"Tools nobody on the team wants to use. Tools that duplicate work the database admin could do faster with SQL. Tools whose only feature is a wrapped Airtable view.",{"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","INTERNAL TOOLS AND ADMIN",[42,45,48,51],{"q":43,"a":44},"Why custom over Retool \u002F Internal?","Retool and Internal are great until your team hits the wall of \"we cannot ship this specific interaction.\" Once a tool actually matters, the custom build is cheaper than fighting the platform for a year.",{"q":46,"a":47},"How long until usable?","Six to ten weeks at the $20k floor for a tool with six views. The team can use a v1 by week three usually.",{"q":49,"a":50},"Do you handle SSO?","Yes. Google Workspace and Okta are the common ones. SSO is in scope at the floor.",{"q":52,"a":53},"Can we self-host?","Yes. Docker image, environment variables documented, deploy guide handed off at launch. We've shipped to AWS, GCP, Hetzner, and bare-metal.","$20k","Admin panels and ops dashboards built right.",[57,58,59,60,61,62],"One internal tool with up to 6 main views","Role-based access control with audit log","Connection to one data source (your DB or API)","Bulk operations with undo on at least one workflow","Deployed to your infra or Vercel","Two-week post-launch support",{},true,70,"\u002Fservices\u002Finternal-tool",[68,71,74,77],{"title":69,"body":70},"Built against your real data","We connect to the database, API, or warehouse you already have. No middleware layer, no proprietary connectors.",{"title":72,"body":73},"Role-based from day one","Roles, permissions, audit log. Not a single admin password shared in a shared 1Password vault.",{"title":75,"body":76},"Designed for speed of use","Keyboard navigation, bulk operations, undo. Internal tools live or die by how fast a power user gets through a queue.",{"title":78,"body":79},"Owned by you","Code, hosting, secrets all in your accounts. No vendor lock to a low-code platform that bills per seat.","Phase-by-phase quote, fixed bid",[82,83],"saas","marketplaces",[85,86,87,88,89],"Multiple connected data sources with cross-source queries","Real-time updates (sockets, presence, live queues)","Complex workflow engines (approval chains, escalations)","Embedded analytics or BI panels","Customer-facing read-only mirror (status pages, partner portals)",{"title":5,"description":33},"Custom internal tools, admin dashboards, ops consoles. Built against your real data, with audit logs, role-based access, and observability. Starting at $20k.","Internal Tools Development | Custom Admin Panels and Ops Dashboards | HARTECHO","internal-tool",[95,98,101,104,107,110],{"name":96,"note":97},"Nuxt 3 + Tailwind","Or Next.js. Whichever fits the team.",{"name":99,"note":100},"Drizzle \u002F Prisma + Postgres","When we own the schema.",{"name":102,"note":103},"Read-only connectors to your DB \u002F API","When we don't.",{"name":105,"note":106},"NextAuth \u002F Clerk","SSO with Google Workspace or Okta typical.",{"name":108,"note":109},"Inngest \u002F Trigger.dev","Background jobs for bulk operations.",{"name":111,"note":112},"Sentry, Better Stack","When the tool is mission-critical for ops.","services\u002Finternal-tool","Custom internal software your team actually wants to use. Operations dashboards, support consoles, content-moderation queues, ops-on-call surfaces.","second","lkzB-DSU9Ur5cxRwWp8yiCBxbfUyxFKwT4JPjIRKTtI",[118,223],{"id":119,"title":120,"body":121,"description":33,"extension":39,"eyebrow":145,"faq":146,"fromPrice":165,"headline":166,"includes":167,"meta":174,"navigation":64,"order":175,"path":176,"pillars":177,"priceNote":80,"related":189,"scales":191,"seo":197,"seoDescription":198,"seoTitle":199,"slug":82,"stack":200,"stem":219,"subhead":220,"tier":221,"__hash__":222},"services\u002Fservices\u002Fsaas.md","SaaS \u002F web app",{"type":7,"value":122,"toc":140},[123,127,130,132,135,137],[10,124,126],{"id":125},"what-a-starter-saas-build-looks-like","What a starter SaaS build looks like",[15,128,129],{},"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,131,21],{"id":20},[15,133,134],{},"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,136,28],{"id":27},[15,138,139],{},"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":141},[142,143,144],{"id":125,"depth":34,"text":126},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"SAAS DEVELOPMENT",[147,150,153,156,159,162],{"q":148,"a":149},"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":151,"a":152},"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":154,"a":155},"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":157,"a":158},"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":160,"a":161},"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":163,"a":164},"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.",[168,169,170,171,172,173],"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",[178,181,184,187],{"title":179,"body":180},"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":182,"body":183},"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":185,"body":186},"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":188},"Schema, migrations, deploy keys, observability. All in your accounts. We work for you, the code does too.",[190,93],"ai-integrations",[192,193,194,195,196],"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":120,"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",[201,204,207,210,213,216],{"name":202,"note":203},"Nuxt 3 or Next.js","SSR-first. Choice depends on your stack and your team.",{"name":205,"note":206},"TypeScript strict","Types derived from schema, no any escapes.",{"name":208,"note":209},"Drizzle or Prisma + Postgres","Migrations checked in, no manual schema drift.",{"name":211,"note":212},"NextAuth \u002F Clerk \u002F Better Auth","Multi-tenant patterns from day one.",{"name":214,"note":215},"Stripe Billing","Subscriptions, metered usage, customer portal.",{"name":217,"note":218},"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":224,"title":225,"body":226,"description":33,"extension":39,"eyebrow":250,"faq":251,"fromPrice":267,"headline":268,"includes":269,"meta":276,"navigation":64,"order":277,"path":278,"pillars":279,"priceNote":80,"related":291,"scales":293,"seo":299,"seoDescription":300,"seoTitle":301,"slug":83,"stack":302,"stem":317,"subhead":318,"tier":115,"__hash__":319},"services\u002Fservices\u002Fmarketplaces.md","Marketplaces",{"type":7,"value":227,"toc":245},[228,232,235,237,240,242],[10,229,231],{"id":230},"what-a-starter-marketplace-looks-like","What a starter marketplace looks like",[15,233,234],{},"Two-sided auth, listings with faceted search, Stripe Connect with payouts, reviews, dispute admin, notifications. Twelve to twenty weeks. The whole flow works end-to-end at launch.",[10,236,21],{"id":20},[15,238,239],{},"Escrow and milestone payouts are a real chapter (fund timing, refund rules, SLA enforcement). KYC verification is its own. Subscriptions for sellers add their own data model. Multi-region marketplaces are roughly 1.5x the scope.",[10,241,28],{"id":27},[15,243,244],{},"Marketplaces where the founder has not yet talked to any of the supply side. Marketplaces where the take rate is unsustainable. Anything where the demand and supply curves don't intersect at any realistic price.",{"title":33,"searchDepth":34,"depth":34,"links":246},[247,248,249],{"id":230,"depth":34,"text":231},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"TWO-SIDED MARKETPLACE BUILDS",[252,255,258,261,264],{"q":253,"a":254},"Can we use Stripe Connect Standard?","For very simple marketplaces yes. But Standard pushes the seller to manage their own dashboard which most marketplaces don't want. Express is the default, Custom when KYC matters.",{"q":256,"a":257},"How long until launch?","Twelve to twenty weeks at the $75k floor for a real two-sided marketplace. Cold-start (getting first listings + first buyers) is yours.",{"q":259,"a":260},"Will it survive 100k listings?","Yes. Search uses Postgres FTS or Typesense with proper indexing. Pagination is keyset, not offset. Performance work is in scope at the floor.",{"q":262,"a":263},"What about tax?","Stripe Tax for transaction tax. 1099-K reporting via Stripe Connect. International is more complex and lands in the scaler bucket.",{"q":265,"a":266},"Can we add a subscription layer?","Yes. Sellers paying for boosted listings or commission discounts is a common scaler.","$75k","Marketplaces that handle real money.",[270,271,272,273,274,275],"Two-sided user model (buyer + seller) with auth","Listings, search with faceting, detail pages","Stripe Connect with application fees and payouts","Reviews and ratings on completed transactions","Admin with dispute queue and audit trail","Email and SMS notifications for both sides",{},80,"\u002Fservices\u002Fmarketplaces",[280,283,286,289],{"title":281,"body":282},"Real Stripe Connect, day one","Express or Custom accounts, application fees, payout schedules, 1099-K reporting. The money flows correctly before launch.",{"title":284,"body":285},"Search that scales","Postgres full-text or Typesense from the start. Faceted, paginated, ranked. Not a \"search later, MVP first\" promise.",{"title":287,"body":288},"Admin for disputes","Every marketplace has disputes. We build the queue, the audit trail, and the resolution flow as part of the core, not as an afterthought.",{"title":78,"body":290},"Code, Stripe account, search index, hosting. All in your accounts. Marketplaces are too operational to outsource hosting.",[82,292],"ecommerce",[294,295,296,297,298],"Escrow holds and milestone-based payouts","Verification flows (ID, business, address)","Subscription tier for sellers (boosted listings, commission discounts)","Multi-region with localized currency and tax","Mobile app for one or both sides (see Mobile)",{"title":225,"description":33},"Custom marketplace development. Two-sided platforms, Stripe Connect payouts, search, reviews, admin, dispute handling. Hand-coded, owned by you. Starting at $75k.","Marketplace Development | Two-Sided Platforms with Stripe Connect | HARTECHO",[303,306,309,312,314],{"name":304,"note":305},"Nuxt or Next + Postgres","Multi-tenant data model from day one.",{"name":307,"note":308},"Stripe Connect (Express or Custom)","Express for speed, Custom when you own the KYC.",{"name":310,"note":311},"Typesense or Postgres FTS","Search faceted, paginated, ranked.",{"name":108,"note":313},"Payout scheduling, escrow timers, dispute SLAs.",{"name":315,"note":316},"Twilio \u002F Postmark","Notifications across two-sided flows.","services\u002Fmarketplaces","Two-sided platforms with auth, search, payouts, reviews, dispute handling, and admin. Built so the cold-start problem is the only problem you have.","VRsMNrT-ed7ePmFqpGFw0uH_KXnbsTY2oQCGFPeKwj8",1779549900379]