How to work with AIpplied Labs
Working with AIpplied Labs takes three steps: a free 20-minute working session to find the problem, a fixed-price build of two to four weeks to fix it, and a handover where you own everything. The person you talk to in the first session is the person who writes the code.
The three steps
-
01
Find it
A free 20-minute working session on the biggest time sink in the business. The work happens live, and the owner leaves the same day with a one-page plan or a quick demo, a fixed price for the first phase, and a straight answer on what isn't worth building.
-
02
Fix it
AIpplied Labs ships work every week against a fixed scope, on the business's real data. The person who ran the working session writes the code, so no detail gets lost in a handoff. One home services build connected five lead sources to the company's CRM in four weeks.
-
03
Own it
Everything is delivered as owned code, on the client's own accounts, with documentation written for the team that inherits it. The second half of the fee is due only when the system passes the acceptance test agreed at the start.
The first two weeks of a build
- Day 1. The working session confirms the scope and sets the fixed price. The plan arrives in writing the same day.
- Week 1. Access to the tools the system plugs into, then the first working piece running on your real data.
- Week 2. You test it on real work and say what's off. Nothing goes live until you've signed off.
How payment works
Half the fee is due on signature. The other half is due when the system passes the acceptance test written into the scope. If it doesn't pass, the second half isn't owed. See pricing for each system.
Common questions
What does the process look like?
Three steps. Working session: 20 minutes on your biggest time sink, and you leave with a one-page roadmap or a quick demo. Build: weekly increments against a fixed scope, and I write the code myself after running the session. Handover: owned code with documentation written for the team that inherits it.
Support continues by arrangement, never as a condition of keeping the system running.
How much of our time will this take?
About twenty minutes for the working session, then your honest feedback once there is something to look at. Progress shows up in weekly increments. Nothing to chase, nobody to manage, and no status meeting to sit through.
Does anyone on our team need to be technical?
No. You describe the problem in plain language; I handle everything technical. The only real asks are about twenty minutes during discovery and your honest feedback once there is something to look at.
When could you start?
The working session is usually the same or the following week. Build slots depend on what I already have running, and the session ends with a real date on it.
What if it doesn't work?
Nothing ships until you have tested it and are comfortable with how it works, so a system that can't do the job never reaches handover. I work in weekly increments for the same reason: problems surface in week one, while they are still cheap.
Are we locked in to anything?
No. You own the code and the documentation outright, nothing is licensed back to you, and nothing stops working if you decide not to continue. I offer support because it is often useful, never because the work depends on it.
Will our team need training?
Very little, by design. Tools that need a training program to survive tend to get abandoned. Handover includes documentation written for whoever inherits the system, in the language they already use for the work.
Will it work with the tools we already pay for?
That is the default. Part of the working session is finding out which tools are already paid for and underused, because the cheapest system is usually the one that runs on what you already pay for.
Where does our data live and who can see it?
In your accounts, under your control, on infrastructure you own. I need access to build, and I hand every credential back at handover.
I scope anything sensitive in the working session before writing a line of code, because getting that wrong is expensive.