Two people. Every project. Clear responsibility.
Steven builds every store. Julie leads every project. From the first reply through launch, you work with the people whose names are on the plan.
Esteben began with a problem inside Steven's own family.
Steven grew up in Jamaica, Queens, watching his father run a business through long days and a lot of manual work. By 2018, one repetitive process was consuming roughly 30 hours every week, time that should have gone back to the business and the people behind it.
Steven taught himself to build a system that handled the work instead. That first build did more than start a career. It set his definition of useful technology: it should solve a visible problem, give time back, and make the person running the business feel more in control.
He later spent years as an in-house full-stack engineer at a DTC wellness brand on Shopify. Working inside one commerce business changes the standard. You see what happens after launch. You live with the theme your team has to update. You learn that a small tracking error can distort decisions, that a slow page can get in the way of a sale, and that a clever build is not useful if nobody else can operate it.
Esteben brings those lessons to independent product businesses that need a better place to sell. Steven remains responsible for every build. Julie leads kickoff, decisions, weekly updates, reviews, and launch coordination. Clients always know who is building the store, who is answering the question, what is included, and what happens next.
Steven turns the plan into a working store you can run.
Steven turns the written plan into the working Shopify store, checks the buying path, and hands it over so the owner can run it.
Before Esteben, he worked in-house across storefront development, analytics, experimentation, and checkout systems for a DTC wellness brand. The technical depth matters because it helps him recognize problems early. The client experience stays plain: what it means, what the options are, and what happens next.
- Self-taught
- Since 2018
- Trained
- In-house on Shopify
- Focus
- Storefront · Tracking · Checkout
Julie is the reason you never chase us for answers.
Julie leads kickoff, keeps decisions and materials organized, sends the weekly written update, coordinates reviews, and guides launch. When a question needs Steven, she gets the answer and brings it back in context.
- 01
Kickoff
One structured call that collects everything the build needs: assets, access, decisions, dates. You leave it knowing the full plan.
- 02
Weekly written updates
Every week, in writing: what shipped, what's next, what we need from you. Not a dashboard you have to check; an update that arrives.
- 03
One point of contact
Questions go to Julie and get answered, or get to Steven and then answered. You are never passed between people who don't know your project.
- 04
Launch coordination
Scheduling, checklists, and the go-live itself, coordinated so launch day is boring. Boring is the goal.
The way we work.
- 01
Write it down.
Scope, price, responsibilities, changes, decisions, and progress should not depend on memory.
- 02
Build for the day after launch.
A store is not successful because the developer understands it. It needs to remain useful to the people running the business.
- 03
Say what is not included.
Clear boundaries protect the budget, the date, and the working relationship.
- 04
Do not invent proof.
If we cannot verify a result, we do not print it. If a project is a concept, we label it as a concept.
- 05
Keep responsibility visible.
Steven stays responsible for the build. Julie stays responsible for the project. If specialist help is needed, the client hears about it before it is added.
Why the site looks this way.
The ruled paper, numbered sections, and written updates come from the same belief: clarity is part of the work. The visual system is a record of where Esteben began: a family business, a visible problem, and a solution written down step by step.