Skip to content

06 — Business infrastructure

The layer nobody sees, that everything depends on.

Rules in Postgres, an access check on every request, 21 scheduled jobs, one enforced price at checkout, and a desktop app that adds no rules of its own.

My role
Product architecture
Built
Aug 2026
Built with
Next.js · Supabase · Vercel · Fly.io · Stripe · Electron
Status
In production at vayrk.com
Vayrk· Exhibit 06 · Business infrastructure
Sample data only
Vayrk Follow-ups on a phone, in a synthetic workspace: ‘Follow-up is paused. Nothing is emailed automatically until an owner or admin turns it back on.’
Follow-ups on a phone, Staging, synthetic workspace. Automation stays off until an owner turns it on.
01 — The approach

Keep the rules in one place.

Business rules live in Postgres. Every rep route checks access on each request, so turning off an employee takes effect at once. Checkout refuses any price except the approved launch offer. The live copilot runs on its own gateway on Fly.io, because a long-lived audio connection cannot run on Vercel. The Vayrk Sales OS desktop app holds no rules, data or credentials of its own.

02 — How it works

Five layers, one source of truth.

  1. Layer 5SurfacesRep portalSales AcademyCustomer CRMWebsite FactoryAdminVayrk Sales OS (desktop)
  2. Layer 4AI servicesVayrk Ops agentsLive Sales CopilotWebsite StudioLead qualificationLead enrichment
  3. Layer 3Core dataPostgres (Supabase)Business rules in the database
  4. Layer 2IntegrationsTwilioStripeResendApolloGoogle CalendarDiscord
  5. Layer 1PlatformSupabase sign-inAccess check per requestVercel + 21 scheduled jobsFly.io gatewaySigned desktop updates

Taken from Vayrk’s repositories and records, October 2026.

  1. 01

    Integrate

    Twilio, Stripe, Resend, Apollo, Google Calendar and Discord, each behind its own webhook or job.

  2. 02

    Automate

    21 scheduled jobs: follow-ups, lead sourcing, calendar sync, commission reconciliation and upkeep.

  3. 03

    Secure

    Role and status checked on every request. The desktop app refuses every permission except copying to the clipboard.

  4. 04

    Control

    Automation has an off switch an owner can see. Follow-up stays paused until an owner or admin turns it on.

03 — Outcomes

What the record shows.

Each figure names its source. Development and Staging results are labelled as such; nothing here is a customer result.

Verified
3,717 / 3,717

Full application test suite passing at the end of every Copilot build phase.

Source: Copilot control record · Sep 2026

Verified
21

Scheduled jobs running the platform’s messaging, lead sourcing, calendar sync and billing upkeep.

Source: Vercel cron configuration · Oct 2026

04 — Built with others

Sign-in, billing, release authority and runtime reliability are owned by Jason Zipp.

Want to build something like this? Let’s talk.

Get in touch Résumé