You do not need to write code to run an AI agency, but someone has to build what you sell. Here is who does it, what you still own, and who this setup is not for.
Lumina··7 min read
No, you do not need to code to run an AI agency, but you do need someone who can. The question is whether that someone is you, a hire, or a fulfillment team you rent. On Lumina Sales it is the third option: you sell and scope, and our engineers build and deliver under your brand. That works well for some people and badly for others, and the difference is worth understanding before you pay for anything.
What does "no code" actually mean for an agency?
It means you do not write the software that ends up running inside a client's business. It does not mean nobody writes it, and it does not mean you can skip the thinking that comes before it.
AI agency software for sales and fulfillment
Custom fulfillment from our engineering team, live AI demos, and a client portal, all 100% white-labeled.
Take a plumbing company that wants an AI receptionist. Somebody has to decide how the voice agent handles an emergency call at 11pm, which calendar it books into, what it says when a caller asks for a price, and where a lead goes when the call ends. Then somebody has to wire that up, test it, and fix it when the client's booking software changes. The first part is business judgment. The second part is engineering.
Agencies that say they are "no-code" usually mean they use visual builders for the second part. One vendor that sells tools to agencies, Ciela AI, argues that you can start without coding, but it also lists the skills you still need: a working grasp of APIs, reading JSON, understanding webhooks, and troubleshooting failed workflows. It also says custom integrations, where a client's tool has no ready connector, can push you into raw API calls. Treat its project percentages with caution. It sells to agencies and does not source them.
So the honest framing is this. You can skip writing code. You cannot skip owning the result.
Who does the building when you do not code?
There are three realistic paths, and they trade money against control.
Learn a visual builder yourself. Tools like n8n and Make let a non-developer assemble automations. This is cheap in cash and expensive in time. You also become the person who gets the 7am text when a client's workflow breaks. We covered the licensing side of this in our n8n post.
Hire a developer. You get someone who can handle odd requests, but you carry salary or contractor risk before you have revenue. We worked through that tradeoff in hiring a developer versus using a white-label stack.
Rent the engineering. This is what Lumina Sales does. Per the fulfillment section on our site, you price the build with the Scope Calculator before you pitch, close the deal at whatever price you set, then get on a call with a developer from our team and scope every detail. They build it, onboard your client through your branded portal, and handle revisions. Your client sees your brand the whole way.
What do you still do yourself?
Quite a lot, and this is where non-technical founders sometimes get surprised.
You run the sales. You pick the trade, find the prospects, run the demo call, and set the price. The live demo builder helps with that, because you can type in a prospect's website and have a custom demo in front of them quickly, but you are the one talking.
You also scope. When you get on the call with the developer, you are the one who knows what the client said they wanted. If you walk in with "they want AI" you will get a vague build and a bill that surprises you. If you walk in with a clean intake, you get what you sold. Our client intake checklist is the list we would want you to have in hand.
And you manage the client relationship. Updates, expectations, renewals, the awkward call when the AI books a job in the wrong city. Nobody can do that part for you, and it is most of what keeps clients paying.
How does the cost work if you are not building it?
The platform is $49 a month. There is no build fee on the plan. Each client build is scoped with an engineer and billed on their time and fees, agreed before work starts, and nothing is charged until the build begins. What you charge your client on top is yours.
We are not going to publish a build price here, because it depends entirely on what you scope. That is the point of the Scope Calculator: you see your cost and your margin before the sales call, not after. For the rest of the numbers, see the pricing section and our breakdown of what it costs to start an AI agency.
One cost you do not carry is the stack of usage bills. The plan includes 100 voice minutes, 500 chat messages and 50 website audits a month, and at a limit the live parts pause until next month. You never get a usage bill. Compare that with building the voice side yourself on a developer platform. Vapi's documentation says its estimate is built from separate transcriber, model and voice components, and its billing page describes usage as a per-minute hosting fee plus the model, voice, transcriber and telephony costs for each call. That is four or five meters you would have to understand and bill around.
When is this not for you?
Renting engineering is a poor fit in a few cases.
If you want to build everything yourself because the building is the part you enjoy, you will feel boxed in. You are paying for someone else's time on work you could do, and you will notice every hour.
If your clients want something deeply unusual, like a custom integration with obscure legacy software, you will need to scope it carefully and expect it to cost more. We can build to a client's needs, but a strange request is still a strange request.
If you cannot tell a good scope from a bad one yet, expect a learning curve. Not having to code does not mean you can stop understanding what you are selling. Run a few demos and a few small builds before you promise anything large.
And if you want a guarantee of results, nobody can give you one. The honest version is that the build is only half of a client's outcome. The other half is how their business handles the calls and leads the AI hands them.
What should a non-technical founder do first?
Do the sales work before the engineering work. Pick one trade, build a demo for a real prospect in it, and put it in front of them. If they bite, scope the build with a developer and price it with the margin visible. If they do not, you have lost an afternoon, not a build budget.
You can start that on the signup page. Build your first demo for a prospect you already know, and see how it feels to talk about the system before you talk about price.
FAQ
Do I need to know how to code to use Lumina Sales?
No. You use the dashboard, the demo builder and the Scope Calculator, and the Lumina Assistant can do things like build a demo or design an onboarding form when you ask in plain words. Our engineers handle the build itself.
Do I need to hire a developer?
Not to take on a project. Access to our fulfillment team is part of what the $49 a month gets you, with each build billed on developer time when you order it. You can still hire one later if you prefer to bring work in house.
Will my clients know Lumina is involved?
The plan is 100% white label. Your logo, colors and web address are on every demo, portal page and email, and your clients do not see the name Lumina. They see you.
What if I do know some code?
Good, because it makes you a better scoper. There is an MCP server and a REST API on the plan, so you can run your workspace from your own tools. You can use them without ever touching the build side.