Contact Us

Offices

Head office — Houston area, TX

+1-346-831-1784

Branch office — Phoenix area, AZ

+1-602-500-3513

Before you write

What does Nurturing Lab actually do?

We are a small, hands-on AI product studio. Instead of slide decks, we build and ship real software — AI-powered mobile and web products taken end to end, from first architecture through launch and self-hosted operations. That same experience is what we bring to advisory work: practical, engineering-grounded help for teams building with AI.

Are you consultants or engineers?

Engineers. The advisory work exists because we have built and launched the systems we are advising on — agent architectures with real tool permissions, LLM features with multi-provider failover, mobile products through App Store review. If an engagement would be better served by us writing the code than by us writing a document, we will say so.

How big is the team?

Small and deliberately so. You work with the person doing the work, not an account manager who relays to a delivery team. That is the main constraint on how much we take on at once, and the main reason a reply will tell you plainly if we are not the right fit.

What if AI is not actually the right answer for my problem?

Then that is the finding, and it is a useful one. Part of the strategy work is mapping where AI genuinely moves the needle for your product and users and where it does not — a plan that tells you to skip a feature has saved you the cost of building it.

How do engagements start?

You describe what you are building and where it is stuck, using the form on this page. You get a reply, usually within one business day, from the person who would do the work. If it looks like a fit, there is one call, then a written scope covering what the engagement includes, what it excludes, what it costs and how long it runs. Nothing starts before you have agreed to that in writing.

Which kind of engagement do I need?

There are four shapes — a discovery sprint, an architecture and hardening engagement, a due-diligence review, and fractional CTO time. They are described in full, including what we need from you, on the How we work page. If none of them fits, say what you are trying to do and we will tell you that rather than fitting you into one.

How do you charge?

Fixed price for scoped work — a discovery sprint or a due-diligence review, where the deliverable is defined up front. Ongoing work such as fractional CTO time is billed monthly against an agreed scope, reviewed quarterly. You get the number in writing before anything starts, and a scope change is a conversation rather than a surprise on an invoice.

Is there a minimum engagement?

The smallest thing we do is a due-diligence review, which runs one to two weeks. Below that, a question you can ask by email is usually better answered by email — and that costs nothing.

Do you take equity instead of fees?

Sometimes, for build and advisory work — if we believe in what you are building, equity or a mix of equity and reduced fees is worth discussing. The exception is technical due diligence, where we will not take a stake under any arrangement. You are paying for an opinion that is worth having precisely because we have nothing riding on the answer, and a stake would quietly destroy that.

Who owns the code and the documents?

You own the work product. Everything built for your system — code, architecture documents, threat models, the evaluation harness and test suites written against your product — is yours, handed over in a form your team can run from. What stays with us is the generic tooling and methods we brought with us or would have built anyway, which we keep the right to reuse. Nothing we retain would stop you replacing us.

Do you work remotely, and in which timezone?

Remote-first, with offices in the Houston area (US Central) and the Phoenix area (US Mountain, no daylight saving). Working hours overlap meaningfully with US and European teams, and most communication is asynchronous and in writing — which means the timezone matters less than it sounds like it should.

Will you sign an NDA?

Yes. Send yours with your first message if the thing you need to describe requires one — we read it before signing, and if a term is unusual we will say so, but that is a conversation rather than a delay.

What happens when the engagement ends?

You keep the artefacts and the reasoning behind them. For build work that means the code, the infrastructure and the operational knowledge to run it; for advisory work, the documents and the decisions behind them. The end of an engagement should not be the moment your team discovers what it does not know.

How quickly do you reply?

Usually within one business day.