This is how a FactoryJet store or AI agent project runs, from the first call to the year after launch: what you get at each step, where you can stop, and how we handle your systems and data.
The terms, in one place
Every FactoryJet store or AI agent project starts with a scoping call with the founder and a working draft on your own data. You then get one fixed price per phase, in writing, paid against milestones. Defects after launch are fixed inside the build price for an agreed cover period. Support after that is optional, with no monthly minimum, and you own the code from day one.
How an engagement runs
The first two steps happen before you sign anything. You can stop after either one, and the demo is yours to judge on your own records.
Bhavesh runs the first call himself. We look at the systems you use, the job you want done, and whether a ready-made tool already covers it. If one does, we say so.
What helps: the systems involved, how often the work happens, who does it today, and a brief or RFP if you have one.
For a store, that is a draft theme set up in your own store with your own products. For an AI agent, it is a run on a sample of your own files and rules, so you can check its output against a job you have already done by hand.
What we need: what starts the work (an order email, an invoice, a form), which systems it touches, and a few real examples, with names removed if you prefer.
You get the scope, a dated plan and one fixed price in writing. Larger projects are split into phases, and each phase is scoped, priced and signed on its own, so you never commit to work you have not seen defined.
No hourly billing. Payments are tied to milestones, such as signing, go-live and the finished integration.
We design, build and connect the systems in the agreed scope. The code sits in a repository you own from the first day of the build, not from launch. Changes to scope are quoted and approved before we do them.
Most stores go live in 3 to 5 weeks. Migrations, ERP links and agents follow the dated plan in your proposal.
We put it live and hand over the accounts. For a store migration, every old URL is mapped to its new page with a single-hop 301 redirect, and the redirect map is part of the scope you sign off.
For an AI agent, a person on your team approves what it drafts until you decide which steps are safe to automate fully.
Defects found after launch are fixed inside the build price, for a cover period we agree before work starts. You do not pay again to get the agreed scope working.
The cover period is written into the proposal, next to the price.
After the cover period, support is optional. Each change is quoted and approved before we do it. We can keep managing the servers, AI models and integrations for you, or hand the whole thing to your team or another developer.
AI usage and hosting can be billed to your own accounts at cost, with no markup from us.
Next step
Send us the job and the systems it touches.
We reply with what we would build first and whether a ready-made tool already does it. If there is work for us, you get a working draft on your own data and a fixed price in writing.
Security and data handling
These are the practices we follow on store and agent builds. If your team needs something specific, such as data that cannot leave your servers, raise it on the scoping call and it goes into the written scope.
One build, in detail
The Washington Law Group accident agent
We will sign your NDA before the scoping call if you need it. Mutual NDAs are also available.
The demo runs on a few of your real records. Remove names and personal details first if you prefer; the demo still shows what the software does.
Your store, ERP, AI and hosting accounts stay yours. The code lives in your repository from day one, so access to it never depends on us.
Workflows connect with API credentials limited to what each step needs, and no credentials are stored in plain text.
For medical and financial teams we can run self-hosted n8n inside your own infrastructure, so the data never leaves it. AI builds can be hosted in UK or EU cloud regions.
On most of our builds the agent drafts the record, such as a sales order, a bill or a quote, and a person on your team approves it.
For clinics and other health businesses we scope which pages and forms handle patient information before we quote. Your practice remains the covered entity responsible for HIPAA compliance.
Recent work
More in all case studies. For what we build, see services; for how quotes are scoped and what drives cost, see pricing.
How we work FAQ
Short answers on demos, pricing, support after launch and how we handle your data.
Yes. Before you sign, we show you working software built on your own data. For a store, that is a draft theme set up in your own store. For an AI agent, it is a demo that runs on your sample files and rules, so you can check its output against a job you have already done by hand. You decide after you have seen it work.
After a short scoping call you get the scope and one fixed price in writing. Larger projects are split into phases, and each phase is scoped, priced and signed on its own. Payments are tied to milestones, such as signing, go-live and the finished integration. We do not bill by the hour.
No monthly minimum. Defects found after launch are fixed inside the build price for a cover period we agree before work starts. After that, support is optional: each change is quoted and approved before we do it. AI and hosting can run in your own accounts, at cost, with no markup from us.
If it is a defect in the work we agreed, we fix it inside the build price during the cover period written into your proposal. Changes and new features after launch are quoted separately and only done once you approve them.
Yes. You own the code and the repository from day one, along with the design files. Your store, ERP and AI accounts stay in your name. You can host it anywhere, change it yourself or hand it to another developer.
Yes. We will sign your NDA before the scoping call if you need it. Mutual NDAs are also available.
We connect with API credentials limited to what each step needs, and no credentials are stored in plain text. The accounts stay in your name. When the data has to stay inside your own infrastructure, we can run self-hosted n8n there.
Yes. AI builds can be hosted in UK or EU cloud regions, and self-hosted n8n can run on servers in the EU. Personal data stays in accounts you control. Whether a setup meets GDPR is your legal team’s call, and we build so they can sign it off.
Most stores go live in 3 to 5 weeks. A migration, a B2B portal or an ERP link takes longer, because it depends on how many records and systems are involved. An AI agent usually starts with one workflow. You get a dated plan with the fixed price, so the timeline is in writing too.
On most of our builds the agent drafts the record and a person on your team approves it: a sales order, a bill, a quote. You decide which steps are safe to automate fully, and that can change once the agent has a track record on your own data.
Start here
Send the systems you use and the work you want done. We come back with a working draft on your own data and one fixed price in writing.