Questions. Asked before almost every project.

The people doing the work. We're a small senior team in New York, and the same people plan it, design it, write the code, run the servers and pick up the phone after launch. Nothing gets passed down a chain.

You tell us what's in the way, and we ask a lot of questions. The call is free and there's no obligation. If we're not the right team for the job, we'll tell you.

Within two business days. A person reads every message and writes the reply, usually one of the people who would do the work.

Enough to keep decisions moving. We need one person who can answer questions within a couple of days and look at work in progress each week. You'll see working screens early, not a presentation at the end.

No. We're based in New York, and most of the work happens over calls and shared screens. When seeing the place matters, like a venue floor or a store opening, we'll talk about a visit.

It depends on what we're building, so we don't publish prices. After the first call we send a written quote with the scope, the price and what isn't included. That's the number we work to.

It often does, once you see the work. We write up the change with its cost and its effect on the timeline, and only start it once you've agreed.

A focused website can take weeks. A platform with billing and customer portals takes months. The quote includes a timeline, and if something threatens it, you'll hear from us early, not at the deadline.

Projects are usually paid in stages: a deposit to start, then payments tied to milestones you can see, like design sign-off and launch. Hosting and care are billed monthly.

Yes, and it's often the right call. A first phase that fixes the most painful thing, like one dashboard or a store finder, tells both of us a lot before anyone commits to more.

You do, once it's paid for: the code, the designs and the content we make for you. The code lives in a repository you can see from the start, not only at handover.

Yes. We build on common, well-documented tools like React, TypeScript, Node, Python, PHP and WordPress, and we write notes as we go. We agree early who changes what, so nobody overwrites anybody.

Yes. We read the code and the setup first, then tell you what's sound, what's fragile and what we'd change. Sometimes the honest answer is to leave it alone.

We reuse know-how and small general-purpose building blocks, never your data, designs or business logic. If a project appears in our work, the client is not named and every screen is redrawn with sample data.

You take everything with you: the code, the logins, the hosting details, a full export of your data and notes on how it all fits together. We help with the move, and once you confirm you have it all, we close our access.

We can. Our managed hosting runs on two servers, checks every site every minute and covers domains, email and storage too. If you'd rather host it yourself or somewhere else, we'll set it up there.

Every minute, each site is requested through the CDN and directly on each server. A site only counts as ready to fail over when both servers serve the same page, so we know which sites can switch before we need them to.

Us. Email or call, and the people who built it pick it up. Because hosted sites are checked every minute, an outage sets off our alerts whether or not anyone has noticed it yet.

Updates, backups, monitoring, small fixes and a set amount of time each month for changes. We size it to what you run, so a single website and a multi-store platform aren't on the same plan. Each plan states how quickly we respond.

Yes. We plan the move so email keeps arriving and the site stays up during the switch, and we tell you before anything changes on your domain. Domains stay registered in your name.

On servers we manage, or in your own accounts if you'd rather hold it. Before we build, we write down where each kind of data lives and who can reach it. We don't sell your data or share it with anyone.

Only the people working on your project, and only what the job needs. Inside the software we build, you set the permissions: which managers see which locations, who can approve and who can export.

When something we build takes payments, the card details go straight to a payment processor, not to our servers or yours. We keep the processor's reference, never the card number.

It answers from the data you connect it to, and only for the people you allow. Before it goes live, we show you which outside services it uses and what each one receives. We choose services whose terms say they don't train on your data.

Send us your questionnaire or your list. We'll answer it plainly, including anything we can't meet, before you sign. Day to day, we limit access to what each person needs, encrypt connections, keep software updated and keep backups.