ai employees you can give a clear job

compare the bill before the job titles

as of 12 november 2026. these are different things to buy, not equal amounts of work. a credit does not mean the same thing across products, and dusk's hosting price does not include ai usage.

buy a result you can describe

start with the work that keeps returning to your desk. can you name the input, the result and the point where a person takes over? that is a better buying question than how many employees an app offers.

a useful first job might be checking a proposal against an attached brief. a poor first job is running sales. the first has an end you can inspect. the second bundles judgment, relationships and promises into a title.

dusk bot lets you define each bot's job in plain words through New bot. change the job later if it turns out to be too broad. a name and a friendly shape help you find it; they do not make it responsible for a business decision.¹

a small roster with separate responsibilities

try these as job descriptions for bots you create, rather than claims about a ready-made staff pack:

• brief reader: read the files i attach, pull out requirements and mark anything the files do not settle.
• draft writer: turn the approved brief into a first draft. keep facts from the brief separate from suggestions.
• second reader: compare that draft with the brief. flag missing requirements and unsupported claims. leave the final wording to me.

attach the relevant documents to their chats. each bot has its own memory and can keep several threads. give the reviewer the source material too; asking it whether another bot sounds convincing is a weaker check than asking what the source actually supports.

if the work becomes a shared conversation, the small-team guide covers handoffs and human ownership.

write the job as a message before making it repeat

send a bounded request first: "read the attached supplier proposal against the requirements file. return missing requirements and questions for me. do not contact the supplier or change either file."

check whether the bot finds the right document, distinguishes a fact from a guess and stops at the requested result. correct the job description when it misunderstands. adding more bots will not repair an unclear brief.

only then make a repeated job. for a folder you deliberately give the bot, try: "every thursday at 4pm, review the proposal files in this project folder. list unresolved questions in this chat. ask me before you change anything."

a routine returns a schedule card with the next runs. inspect it, watch the early runs, and use Pause if the job keeps needing repair. local routines need your computer awake and the app open.⁶

read the costs as separate decisions

dusk has no model of its own. ai usage is billed by your ai provider on your plan with them. a cloud plan pays for the computer that keeps bots running, not an unlimited supply of thinking. check your provider's current terms before choosing how to sign in.

work use needs a work license even when you run the app on your own machine. pro includes one for one person; team plans start at $100/month. for a separate work license, check pricing for the option you need.

for another buying model, sintra offers role-based helpers. lindy prices its team offering by active user and credits. compare the tasks you need with the credits and billing commitment, rather than treating a monthly headline as your finished-work budget.

what still needs a human employee

keep a person responsible for customer promises, hiring decisions, disputes and final approval of public claims. use bots to prepare material for that person. a neat draft can still misunderstand the situation.

there is no measured time-saving or success-rate claim behind this page. judge a trial against your actual work: how much did you need to correct, what did it miss, and was reviewing it easier than doing it yourself? do not count a task as delegated while you are quietly redoing all of it.

a human hire and a bot are different decisions. if you need someone to take responsibility, build relationships or handle unclear situations throughout the day, a list of bot roles is not a staffing plan.

start without giving the whole business away

use one non-sensitive document and one job. connect apps only when that job needs them, and allow each bot only the relevant access. reading and drafting are separate from sending: sends ask first unless you allow a daily amount. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. other app changes are not documented as asking automatically. keep access read only, or write "ask me before you change anything" into the job.⁷

keep the trial if its work is useful after review. narrow it if the checks are taking over your day. the cost guide can help you think through the bill once you know which job is worth keeping.