Hiring a role
Pick a pre-built sales, support, marketing, or ops AI Employee from the workspace in a couple of clicks.
Guide — — by Mahmoud Zalt
A plain-English guide for non-technical founders on where to start with AI: hire one pre-built AI Employee, brief it like a person, and skip the building entirely.
If you are not technical, most AI advice makes the problem worse. It tells you to learn prompt engineering, compare models, or wire up an automation tool, and every one of those is a detour away from your actual business. The message underneath all of it is that you have to become a builder before you get to be a user, and that is exactly the wall that stops non-technical founders from starting at all.
An AI Employee removes that wall by design. Instead of a toolkit you have to assemble, it gives you a pre-built role with a personality, skills, and tools already wired in. You hire it, tell it who you serve and how you sound in one paragraph, and it starts working. There is no model to choose and no prompt to engineer. The interface is a conversation, which means the one skill you need is the one you use every day: describing what a good job looks like, in your own words.
Almost nothing technical. You do not need to know how a language model works any more than you need to understand an engine to drive. What you do need is clarity about your own business: who your customer is, what you sell, how you like to sound, and what a good result looks like for the task at hand. That is knowledge you already carry, and it is the only input the AI Employee genuinely depends on.
The mental shift that makes this click is to stop thinking of AI as software you operate and start thinking of it as a hire you manage. You would never write code to onboard a new assistant. You would tell them about the business, show them a few examples of good work, and correct them when they got something wrong. That is precisely how you work with an AI Employee, which is why being non-technical is not a disadvantage here. Managing people is the exact skill the tool rewards.
Pick a pre-built sales, support, marketing, or ops AI Employee from the workspace in a couple of clicks.
Describe your business, customer, and tone in one paragraph. No prompt syntax, no special phrasing.
Authorize your inbox, CRM, or calendar with a login. The Employee already knows how to use them.
Edit or reject an output and say why, in normal language. The Employee learns your standards from it.
Starting is far simpler than the surrounding noise makes it seem, because the platform handles everything that would normally require a technical person. You are not configuring anything. You are hiring a role and teaching it your business the way you would teach a new hire. The steps below are the entire path, and none of them ask you to touch a setting you would not understand.
Two pieces of advice from watching non-technical founders start. First, be specific in your brief and your corrections, because vague guidance produces vague work, exactly as it would with a human hire. Say what you actually want instead of hoping it guesses. Second, do not wait until you feel ready or informed enough. You learn to work with an AI Employee by working with one, and a week of real corrections teaches you more than a month of reading about AI ever will.
Once your first role is running and you have felt how briefing and correcting works, adding more is the same motion repeated. There is no new technical skill to acquire between your first AI Employee and your fifth. This is the quiet reason the workforce model suits non-technical founders so well: the thing you got good at, managing a role in plain English, is the only thing you ever need to get good at, and it transfers to every role you add.
The honest reassurance is this: being non-technical is not the handicap you have been told it is. The founders who struggle with AI are often the ones who over-index on the machinery and under-index on the management, and management is your strength. If you can clearly explain a job, judge whether work is good, and give a useful correction, you already have everything the tool asks of you. The rest is handled for you, on purpose.
No. A pre-built AI Employee is briefed in plain English, closer to a job description than a prompt. You describe your business and correct the work in normal language. There is no special syntax to learn and no model to configure, because the technical setup is done for you.
Start with the single job you most wish someone else were doing, usually sales outreach, customer support, content, or reporting. Beginning with one role lets you learn how briefing and correcting works without spreading your attention, and the lesson transfers to every role you add later.
That is expected and easy to fix. You correct an AI Employee the same way you would a new hire: edit the output, say what you wanted instead, and it calibrates. Your first week of corrections is how it learns your standards, so imperfect early briefs are part of the process, not a failure.
Sistava starts at 49 per month with credits bundled in and no per-seat surcharge, so a non-technical founder can hire one AI Employee, run it on real work, and judge the value from results rather than a large upfront bet.
Yes, because the skill the tool rewards is management, not technology. If you can explain a job clearly, judge whether work is good, and give a useful correction, you have what it needs. The machinery is handled for you, and you interact through a normal conversation.
Where to start with AI as a non-technical founder comes down to one move: hire a single pre-built AI Employee and manage it in plain English, the way you would a new assistant. Skip the courses on prompting, the model comparisons, and the automation builders, all of which are detours from your business. Pick the role you most want off your plate, describe your business in a paragraph, connect a couple of accounts, and correct the first outputs. Do that, and you will discover the thing nobody tells non-technical founders: your people skills were the qualification all along.