// angle · 02
Build
& integrate.
Real sites, real integrations, real products.
Full builds and the moving parts that make them work — auth, payments, CMS, reservations, analytics, AI features. The studio has shipped this work across restaurants, e-commerce, enterprise SaaS, edtech, FinTech, and cybersecurity since 2010. Pragmatic stack choices. Code your next dev won’t hate inheriting. Performance budgets that hold.
// what you walk away with
Production-grade output, not a demo.
- A working build at production quality — site, app, or integration
- Full source code, handoff doc with architectural reasoning, walkthrough video
- Deploy pipeline configured, monitoring set up, performance budget in place
- CMS content modeled (when applicable) + editorial training for your team
- Two weeks of free post-launch support included
// the full breakdown
Eight things this angle covers.
Most engagements pick one — sometimes two when they're tightly coupled. Never four — that's a hire, not a contract.
-
Full-site builds
A complete marketing or product site on the right stack for your team and content. Astro for content-first sites, Next.js for product apps, Webflow for marketing teams without engineering, WordPress where it's the right call. The right stack is the one your team can maintain.
What's included
- Discovery + content modeling
- Design system + component library
- CMS implementation + content migration
- Performance + accessibility baked in from day one
- Deploy pipeline + monitoring
- Handoff doc + walkthrough video
Deliverable
Live site at production URL + complete handoff package
Typical format
6–16 week full build
-
Restaurant + hospitality web
Built for restaurants, hotels, wellness studios, and service businesses where bookings, menus, and customer flow are the product. The studio has been shipping this work since 2010 — from a 4-table neighborhood spot to multi-location regional groups.
What's included
- OpenTable / Resy / SevenRooms reservation integrations
- Dynamic menu systems (CMS-driven, staff-updateable)
- Online ordering + delivery (DoorDash, ChowNow, custom Stripe)
- iPad POS / order-entry interfaces
- Virtual tours + photo galleries
- Google Business Profile + Yelp integration
Deliverable
Live site + admin walkthrough for staff who actually use it
Typical format
4–8 week sprint or full build
-
E-commerce + storefronts
Stores that actually sell. Shopify for speed of iteration. Custom Stripe when control matters. Headless when the experience needs to be unique. Most engagements include payments, inventory sync, shipping calc, tax, and the email + analytics tie-ins that turn one-time buyers into repeat customers.
What's included
- Product catalog modeling
- Stripe / Shopify integration
- Cart + checkout flow optimization
- Inventory sync (manual, automated, or hybrid)
- Shipping + tax integration
- Post-purchase email + lifecycle automation
- Analytics + attribution tie-in
Deliverable
Working store + handoff doc + first-week monitoring
Typical format
6–12 week build
-
AI integrations
AI features built to ship, not demoware. Streaming chat, RAG with citations, tool-using agents. Provider-agnostic — Anthropic, OpenAI, Mistral, open-weight via Replicate. Includes the boring-but-critical parts: eval harness, rate limits, cost monitoring.
What's included
- Provider selection + cost modeling
- Streaming UI patterns (chat, autocomplete, transcripts)
- RAG pipeline with vector store + reranking
- Function-calling / tool-use layer
- Eval harness + regression suite
- Rate-limit + cost monitoring
Deliverable
Working AI feature integrated into your product + ops guide
Typical format
3–6 week sprint
-
Custom apps + admin dashboards
The internal tools your team needs but no SaaS quite fits — admin panels, ops dashboards, customer-facing portals, internal analytics. Usually Next.js + Postgres + auth, but the stack follows the team.
What's included
- Discovery + data modeling
- Auth + role-based access
- The UI itself (responsive, accessible)
- Deploy + monitoring
- Documentation + admin training
Deliverable
Live app + handoff doc + training session
Typical format
4–10 week sprint
-
Martech + CRM integrations
Connect the marketing stack you have so the data flows where it needs to. Marketo, HubSpot, Salesforce, Clearbit, Drift, the rest. Identity resolution, attribution, lead routing, lifecycle automations — the plumbing that makes the rest of the stack worth paying for.
What's included
- Data layer + identity resolution
- Form + CTA integrations
- Campaign attribution wiring
- Lead routing + scoring
- Lifecycle automation flows
- Monitoring + alerting
Deliverable
Working integrations + admin docs + monitoring dashboard
Typical format
2–6 week sprint
-
CMS implementations
A CMS your team actually wants to use. Webflow CMS for marketing speed. Sanity for structured content. Contentful for enterprise governance. Custom when nothing else fits. Including: content modeling, schema design, roles, editorial workflows, migration, and the training that makes it stick.
What's included
- Content modeling + schema design
- Role-based access control
- Editorial workflows (draft, review, publish)
- Content migration scripts
- Editor training + documentation
- Preview / staging environments
Deliverable
Live CMS + editorial training session + migration completed
Typical format
3–8 week sprint
-
Reservation + booking systems
For service businesses where availability is the product — appointments, classes, consultations, lessons. Calendar logic, availability rules, deposits, reminders, no-show handling, staff scheduling. From a yoga studio to a multi-location wellness brand.
What's included
- Calendar logic + availability rules
- Payment integration (deposit / full)
- Email + SMS reminders + confirmations
- No-show handling + cancellation policy
- Staff scheduling + capacity rules
- Admin dashboard + reporting
Deliverable
Working booking flow + admin guide + first-week support
Typical format
4–8 week sprint
// how i approach this
Four working principles.
- 01
The right tech for the team that'll maintain it.
Webflow for marketing teams. Astro for content sites. Next.js for product apps. WordPress when it's the right call. The wrong stack choice costs ten times more than the right one over five years.
- 02
Integrations need an owner.
Every integration has a clear name on it. No "the SDK handles it." Someone's name, someone's job. Including monitoring + alerting so you find out before your customers do.
- 03
Migrate by parallel run.
New thing runs alongside the old until it's proven. Then cutover with a redirect strategy and rollback plan. No "go live and pray."
- 04
Performance is part of the build, not a polish step.
Perf budget gets set on day one and held throughout. Lighthouse 90+ is a baseline requirement, not a stretch goal.
// frequently asked
Logistics, specifically for this angle.
-
What stacks do you actually use?
Astro for content-first sites, Next.js for product apps, Webflow for marketing teams that don't have engineering, WordPress when the ecosystem and team make sense. The right stack is the one your team can maintain after I leave.
-
Can you fix an existing build?
Yes — usually starts as a one-week audit, then a scoped intervention. About 40% of builds I take on are existing codebases that need surgical work, not a full rebuild.
-
Do you do React Native / mobile apps?
Web only. PWAs and responsive web — yes. Native iOS / Android — I'll partner with a mobile dev if you need both.
-
Hosting recommendations?
Netlify and Vercel are defaults for static + Next.js. Cloudflare Workers for edge logic. Bare AWS / GCP when there's a specific reason. For WordPress, WP Engine or Kinsta.
-
Will you maintain the build after launch?
Two weeks of free post-launch support included. After that, a small retainer is available for ongoing tweaks and additions.
-
Can I bring my own design?
Absolutely. I happily implement someone else's design well. Most agency work comes in this shape.
-
Restaurant systems — what's realistic for a small spot?
A solid menu site with OpenTable integration, photos, hours, and the basics ships in 4 weeks. Add ordering or iPad POS and we're looking at 6–8.
// ready when you are
Let's build the thing.
A paragraph about what needs to exist is all you need to start.