Web Development Agency

Overview

Building a web development agency with co-founder Jahmir Swopes around a preconfigured kit (AWK) — a shared engine of auth, studio, data, and add-ons we reuse across client and venture sites. Same foundations, different bodywork. The public agency brand is still taking shape; the system behind it is already powering real projects.

The problem

Without a shared base, every new site restarts from zero — different auth patterns, different admin tools, different update paths. That slows delivery, breaks continuity, and makes security and maintenance harder over time.

The solution

AWK is the agency’s internal operating system for the web — preconfigured settings and building blocks so every project shares the same secure core. Updates, auth, and studio patterns stay consistent; the brand and experience change per client.

My role

Founder · Product Architecture · Engineering

Process

Codified what worked on BlueSky and Triple Take into a reusable starter: Auth.js, Prisma/Neon, an admin studio, and bolt-on modules. New projects assemble from that kit instead of reinventing the stack.

Key features

• Shared Auth.js + Prisma/Neon core
• Admin studio patterns reused across sites
• Bolt-on modules instead of greenfield stacks
• Security and update continuity by default

Tools and technologies

Results

• One reusable base across ventures and client work
• Faster builds with shared auth, studio, and data patterns
• Easier updates and security continuity between projects
• Proven on BlueSky and Triple Take before wider agency use

What I learned

• The agency brand can wait; the kit cannot — reuse only works if the core is boringly consistent.

Status and next steps

Name and launch the public agency brand while continuing to harden AWK on live ventures.