Production platform case study
Live production platform
Viewprint Academy
A membership and commerce business where I work across product, engineering, community management, commercial decisions, staff operations, events, and a Discord-native member experience.
- Role
- Embedded product, engineering, and operations partner
- Scope
- Full production monorepo
- Core work
- Product, community, commercial, and platform operations
- Status
- Live and actively operated
Context
One business, many connected operating surfaces.
Viewprint Academy needed to operate as more than a storefront or course site. Membership access, product plans, staff work, finance, community roles, creator programs, support, and automation all had to behave as parts of the same platform.
I work as an embedded product and operations partner, not only as the person building the software. Alongside architecting and engineering the platform, I advise on community management, operating processes, offers and sales, event organization, product and community copy, and the operational implications of contracts and agreements.
A customer can move through plans, products, onboarding, and community access while staff handle finance, support, creator activity, and exceptions behind the scenes. Treating each of those areas as an isolated feature would create duplicated state and manual reconciliation.
The system needed clear ownership of product data, durable reactions to business events, and interfaces that exposed enough operational detail for staff without making customers think about the machinery underneath.
System
What I lead and build
01
Products, plans, and onboarding
Customer-facing product and plan flows, forms, onboarding state, account access, and the permissions that connect commercial decisions to the rest of the platform.
02
Durable visual automation
A visual workflow editor backed by durable Inngest execution, allowing product and operational events to drive reviewable multi-step automations rather than fragile request-time scripts.
03
Discord-native community operations
One event-driven Discord bot, signed webhook handling, role and access synchronization, and community actions connected to the platform source of truth.
04
Creator bounty pipeline
Structured creator opportunities, submissions, review states, and staff operations that turn an informal community process into a visible product workflow.
05
Unified ticketing and staff work
Support and operational records designed around ownership, status, communication, and the staff actions required to move work to completion.
06
Deployable platform services
Application services, storage, event processing, deployment configuration, and operational boundaries designed to run as one maintainable platform.
07
Community and event operations
Guidance on how the community is structured and managed, support for organizing member events and webinars, and alignment between platform behavior, moderation, staff responsibilities, and the member experience.
08
Commercial and operational guidance
Offer and sales support, product and community copywriting, management input, and review of contracts and agreements from an operational perspective so business commitments remain practical to deliver.
Architecture
Product and operating decisions that kept it coherent
Model business events explicitly
Commerce, access, creator work, and community activity produce events with clear contracts. That lets connected features react without coupling every product surface directly to every service.
Separate requests from durable work
Long-running and failure-prone tasks run as observable background steps with retries instead of holding a browser request open or silently failing after the response.
Treat staff interfaces as product surfaces
Finance, support, automation, and creator operations received deliberate workflows and interface hierarchy instead of being left as raw administrative tables.
Verify every external boundary
Webhook signatures, typed payloads, authorization, and explicit state transitions reduce the risk of an external event changing access or operational records incorrectly.
Design community operations with the product
Membership rules, moderation, events, staff responsibilities, and the member experience are considered alongside the software instead of being treated as separate community administration.
Connect commercial promises to delivery
Offers, sales language, copy, and agreements are reviewed against the platform and operating capacity so the business can deliver what it communicates.
Result
A platform that can operate its own complexity.
- Customers move through a coherent membership and commerce experience while connected services carry access and community changes into the rest of the platform.
- Staff can operate finance, support, creator programs, and automation through purpose-built product surfaces instead of relying on disconnected manual records.
- The workflow engine provides a durable place to extend operational behavior as the business adds events, integrations, and review steps.
- The monorepo keeps shared contracts, product interfaces, operational services, and deployment concerns close enough to evolve together.
- Product, community, event, and commercial decisions can be evaluated together instead of separating business advice from the systems and people responsible for carrying it out.
Related services
Building something with similar complexity?
Show me what you're buildingShare the roles, workflows, or integrations that need to work together. I'll help turn the difficult parts into a clear, buildable system.