A Alvarez & Co Tom Alvarez TA
$6.5K No close date
$650 weighted SKWebsites built like software.
Client sites built natively in Terminal, our own site builder — with real classes your team can edit — and custom applications for when the work outgrows a website.
Inspector h1
h1.hero-title3
Typography
FontInter
Weight
Line height1.04
Colour#0b1220
3 elements across the site use this class. A change here reaches every one of them.
One class, every page: a change to .hero-title reaches each heading that carries it. We build this way in Terminal.
$3,000
Web builds start at
3 business days
To a fixed written proposal
Terminal
Built natively
60 days
Of post-launch support, included
Built natively, in Terminal.
We build client sites in Terminal, the site builder inside Stacklumen, and the rule is simple. Every element is styled with real classes, and nothing is held together by code embeds, so your team can edit any page without filing a ticket.
Editable by your team, not by ticket
Native classes and components throughout, so marketing can change copy, swap images and publish new pages without a developer in the loop. The editor stays readable to whoever opens it next.
A CMS that survives growth
Collections for work, posts, team and docs — modelled once and reused across templates. Adding the fortieth case study costs the same as adding the fourth.
No embeds holding it together
Styling lives in real classes, not in a block of CSS pasted into an embed. Embed CSS is invisible to the editor and to the next person, which is how sites become unmaintainable.
The right tool for the site
Terminal publishes to a staging link and then the site’s own domain, and keeps every deployment, so a rollback is one step. The proposal says what we recommend and why.
Fast because of how it is built
Clean markup, right-sized images, and a stylesheet that stays small as the site grows. Speed is a consequence of construction, not a plugin you add at the end.
When a website isn't enough.
Some work needs accounts, payments, dashboards or real data behind it. That is an application, and we build it as one rather than bending a website into the shape of something it was never meant to do.
Lumen Dental $12.0K in Contacted, day 17.
- Value$12.0K
- Weighted$3.0K
- OwnerAna Ruiz
- SourceWebsite
Nothing booked next.
Won. Lumen Dental is a client now.
Team only. Clients never see notes.
- Call Priya wants the proposal by Friday.
- Email Sent the discovery questions.
Astro and React
Server-rendered where it matters, interactive where it helps, and served from the same domain as your marketing site rather than a subdomain of its own.
Accounts, billing and data
Clerk for authentication, Stripe for payments, Supabase for data. Proven pieces, wired carefully, so there is nothing exotic to maintain later.
One system, two surfaces
The marketing site and the application share one visual language, so moving between them never feels like changing companies.
The stack, and why.
Nothing here was chosen for novelty. Each piece earns its place by removing work later — either yours, or ours on your behalf.
Our own builder, for the sites we build
Terminal is the site builder inside Stacklumen: a canvas over real HTML and CSS, four breakpoint layers you author rather than preview, CMS collections, and a publish button that puts the site on a staging link and then its own domain. Every deployment is kept, so rolling back is one step.
How Terminal works →- Editor
- Visual canvas, code in StackIDE
- Styling
- Named classes
- Breakpoints
- Four authored layers
- Content
- CMS collections and forms
- Publishing
- Staging link, then your domain
- Desktop
- StackIDE, for Mac and Windows
Astro and React, rendered on the server
Astro renders on the server by default and ships almost no JavaScript, so pages arrive fast. React is used only where interaction genuinely needs it — dashboards, forms, live state. TypeScript end to end, so the application and the data it reads agree with each other.
See the portfolio →- Rendering
- Server-first, with Astro
- Interaction
- React, where it helps
- Language
- TypeScript
- Deploys
- An edge network
Managed services, not homemade ones
Clerk handles accounts, Stripe handles billing, Supabase handles data. Each is a problem we deliberately do not rebuild — authentication and payments are where custom code goes wrong most expensively. Your budget goes into the part of the product only you can build.
How we work →- Accounts
- Clerk
- Payments
- Stripe
- Data
- Supabase Postgres
- Resend
How a build actually runs.
No black box, and no surprise invoice at the end. You see the work every week, and the scope is written down before anyone starts.
-
Scope, written down first
-
Built in the open, demoed weekly
-
Launch without drama
-
Sixty days of support
-
You own all of it
Recent builds.
Every site below is live. Open any one for the scope, the stack behind it, and what actually changed for the client.
Tell us what you're building.
You get a fixed scope and timeline back within 3 business days — or an honest no if we are not the right fit for it.