A client portal for agencies and the teams they serve. Project status, async approvals, file delivery, and Stripe-backed billing — all in one workspace.
A component library application. Browse, preview, and copy production-ready Webflow embeds and React components with live previews and one-click copy.
A Webflow-native AI co-builder trained on our patterns and embed library. Generate animation timelines, debug class conflicts, translate Figma to embeds.
Production-grade applications, internal tools, and SaaS platforms on a modern TypeScript stack. Eight to twelve week sprints with full code ownership at handover.
Pixel-honest Webflow sites with hand-rolled GSAP animations, Lenis smooth scroll, and embedded systems tuned to platform limits. Dark mode and accessibility included.
Tools we're building, in public.
A client portal for agencies and the teams they serve. Project status, async approvals, file delivery, Stripe billing.
A component library application. Production-ready Webflow embeds and React components with live previews.
A Webflow-native AI co-builder trained on our patterns and embed library.
A working software company, documented not pitched.
Company
How we think about who the web is for, who builds it, and what we owe the communities we work inside.
What we hold to — access, dignity, and a refusal to confuse polish with progress.
Concrete mechanics — pro-bono hours, accessibility floors, and revenue we route outward.
Where our attention goes — housing, mental health, and the long work of charity.
A small business in Lexington and a venture-backed startup in San Francisco use the same browsers, the same protocols, the same standards. On paper, that's equality. In practice, the polished, performant, accessible web is built for whoever can afford to commission it — and the rest get templates, dropdowns, and the quiet sense that the internet wasn't really designed for them.
That gap is the part of our work that's hardest to ignore. Most of what we build is paid client work, which we're glad to do well. But the choices that come with running a studio — what to charge, who to take on, what to give away, what to refuse — add up to a position, whether we name it or not.
So we're naming it. This page isn't a list of accomplishments. Stacklumen is small and still early in this work. Most of what's written below is closer to intention than to track record: a statement of where we want the company to be a few years from now, and a note on the one or two concrete things we're doing today. We'd rather write it down honestly and answer to it than dress up small beginnings as a finished philosophy.
The thesis underneath all of it is simple: good work is shared work. The tools that make a digital presence cost what they cost, but the knowledge, the access, the dignity of a well-made thing — those don't have to be rationed. They're rationed because we keep choosing to ration them. We'd like to choose differently, in the small ways we can now, and to grow into the larger ones over time.
Three positions that shape how we want Stacklumen to operate as it grows. Some of these are already how we work. Some are aims we're still getting to. We've written them down so they're harder to drift from.
A site that isn't accessible isn't really done. Screen-reader navigation, keyboard focus, sufficient contrast, semantic structure: these aren't features for a subset of users. They're the minimum description of a site that functions. We care about getting this right on every build, and we're working toward making accessibility a default starting point rather than a question that comes up halfway through.
This applies upward too. We try to write proposals, contracts, and onboarding documents in language that doesn't require a designer to translate. The work shouldn't be legible only to the people who already know the field.
Not every business comes to us from the same starting line. A second-generation family business, a first-time founder without a network, a nonprofit running on margin — these aren't equivalent to a funded startup with a brand budget. We try not to pretend they are. We charge different rates for different contexts, and we want to keep finding ways to make good digital work more reachable for organizations that have historically been priced out of it.
When we can't take a project on at all, we try to leave the person we're declining better off — with a referral, a template, a few hours of guidance, or just an honest reason. The instinct to be useful doesn't disappear just because we said no.
The work intersects with people's livelihoods, their stories, their public image. We won't take on engagements that ask us to misrepresent a product, dark-pattern a user flow, or build something whose primary purpose is to extract from people who have less power than we do. That's the line, and it's already been tested a few times in the form of inquiries we passed on.
On the inside of an engagement, the same standard applies to how we treat clients and how we expect to be treated. Disagreement is fine. Disrespect isn't. We try to make this clear early, in writing, and to mean it.
Principles without practice don't mean much. Here's what's actually in place today, and what we're working to put in place as the company grows. We've labeled which is which.
Three areas we care about as a company and want to be supporting in real, sustained ways. We've kept the framing thematic for now because the specifics are still being worked out — partners we trust, contributions we can actually sustain, and ways of being useful beyond writing checks.
Housing insecurity is one of the most visible and most underserved problems in the communities our work touches. Shelters, transitional housing programs, and the networks of services that hold people through hard seasons rarely have the kind of digital infrastructure they need. This is an area we want to support as Stacklumen grows — both through giving and, eventually, through the kind of pro-bono work we know how to do well.
The reduction in stigma over the last decade is real and worth defending. But awareness alone has limits — you can be very aware that you need help and still not be able to find a clinician, afford a session, or get past the part of yourself that thinks you should handle it alone. The gap between recognition and access is where most of the work still is, and it's one of the spaces we want Stacklumen to commit meaningful time and resources to over time.
A one-time donation is an event. A standing commitment is an infrastructure. We want Stacklumen to operate more like the second than the first — recurring contributions, multi-year relationships, attention paid in the off-season when the spotlight has moved elsewhere. Food banks aren't only needed at Thanksgiving. Shelters aren't only needed on the coldest night. The work is steadier than the headlines, and the giving should be too.