How working with us goes
Most companies describe their process in a way that could describe any company. This is the specific version, including the parts that are inconvenient for us to say.
What we build is the capability side. help@jwlabs.ai is how to start.
The first email
Write to help@jwlabs.ai. There is no form, no discovery-call scheduler, and nobody in front of it.
What is useful in a first email: what the software has to do, who it is for, and what is forcing the timing — a launch, a contract, a platform deadline, a thing that is currently done by hand. A paragraph is plenty. A specification is welcome and not expected.
What happens next: you get a real answer from someone who has read it. That answer is either "yes, and here is what we would want to know next", or "no, and here is why, and here is the shape of company that does this well."
We tell you no, quickly
More often than a company trying to fill a pipeline would admit to.
Sending you elsewhere costs us one email. Taking on work that is the wrong fit costs both of us months and ends with a project neither party wants to talk about. The specific cases where we will say no are listed on the services page rather than left for you to discover in week six.
We agree what "done" means before starting
Not a fifty-page specification that nobody reads after signature. A short, specific, written statement of what the software will do — behaviour, and the conditions under which each piece is finished.
The point of writing it down is not ceremony. It is that "done" should be a fact rather than an opinion. Without that, the end of a project is a negotiation between two tired people, and the person with more stamina wins rather than the person who is right.
If we cannot write that statement for your project yet, that is worth knowing before money changes hands — and it usually means the next piece of work is a short paid exploration rather than a build.
You talk to the people building it
There is no account manager, no delivery lead and no weekly status call whose purpose is to have happened.
The trade is real and you should weigh it. What you get: the person answering your question is the person who wrote the code, so the answer is the actual answer and not a relayed one, and a decision does not have to travel through anybody. What you give up: the reassurance apparatus — no dashboard with a green light on it, and no account team whose job is to tell you it is going well.
What you hear from us while it is happening
Short, specific, and including the bad news. What is finished, what is not, what changed, what we got wrong.
That last one is the load-bearing part and it is the same standard the rest of this site is held to. This website publishes which of our own products are not built, which accessibility work has not been done, and what the security page will not claim. We are not going to hold our own shop window to that standard and then send you a status report with the difficult column removed.
And if a date is going to slip, you hear it when we know, not on the date. A schedule is a forecast; the useful thing about a forecast is how early it updates.
Estimates, honestly
We will estimate. We will tell you what we think something takes and what the estimate is sensitive to.
We will not quote a fixed price for a fixed scope that nobody has specified. Not caution — arithmetic. The only way to hit a number set before the problem is understood is to cut something, and the thing that gets cut is the part you cared about, because it is always the part that turned out to be hard.
We will not pad an estimate to protect ourselves and call it a buffer. Where something is genuinely uncertain we would rather name the uncertainty and agree how to reduce it cheaply — usually by building the risky part first.
We would rather ship a shorter list that works
A recurring decision in every project: four features that mostly work, or two that work.
We will argue for two, every time, and we will lose that argument sometimes because it is your product. What we will not do is agree to four and then quietly deliver four half-features and a status report that says green.
Ownership, and what happens if we stop
You own what we build for you — the code, the data, the accounts it runs in. That is the default and we are not interested in arrangements where it is not.
We will not build you something only we can maintain. Any project we hand over should be legible to whoever comes next: written down, tested, and deployable by someone who was not in the room. The approach to dependencies is part of the same instinct — a build that needs four hundred packages and a specific machine is a build you cannot take anywhere.
It is worth raising early rather than worrying about later, and we will give you a straight answer about it.
What we will not do in your product
The same commitments our own products are held to. They do not come off for a fee.
No dark patterns. No manufactured streaks, no infinite scroll where a list would do, no notification bait, nothing designed to make leaving hard.
No advertising surveillance we would not accept ourselves. We will not bolt a tracking SDK into your product and then help write a privacy policy that talks around it.
No claim we cannot support — not in the software, not in the store listing, not in the privacy policy. If a document has to say something is true, it has to be true, and where a decision has not been made the document records the silence rather than filling it in.
That third one is a genuine constraint on what we will put our name to, and it is better to read it here than to discover it during a submission.
Practicalities
Where we are. JW Labs LLC is a California limited liability company. We work remotely and we are happy on a call in most time zones with a bit of notice.
How to reach us. help@jwlabs.ai, which is the only channel — no phone line and no chat widget. The contact page says what to include.
Rates and terms. Not published, because they depend entirely on the work. Ask, and you will get a straight answer rather than a brochure.
The honest summary
JW Labs LLC has two real products you can open right now — 4a and longlive.
What that gets you is software you can inspect yourself rather than a description of it, a website that publishes its own gaps, and a first email that gets a real answer from the person who would do the work.