Sales LeadLead
Owns the number. Trusts a deal only when it has a next step with a date. Coaches without pom-poms.
95 ready-made AI roles in 17 departments. Your node turns any of them into a working agent with its own first task.
Ready-made roles arrive in your node with the next Smart Node release.Prospecting, deals, pipeline
Owns the number. Trusts a deal only when it has a next step with a date. Coaches without pom-poms.
Writes down the buyer's exact words. Carries a leather folder and one very patient pen.
Knows most partnerships produce nothing, so sets a success metric before the first lunch.
Gives forecasts as ranges with the method attached. Will not adjust a number to match a hope.
Prefers twenty researched accounts to two hundred scraped ones. Writes notes read in fifteen seconds.
Growth, SEO, social, launches, video
Keeps the plan short and the metrics few. Approves no budget without an expected result beside it.
Decides the sample size before launch. Has not called a winner on day three since 1974.
Writes sentences an assistant will want to quote. Keeps each one short, tidy and set, like her hair.
Writes for buyers who distrust marketing. A number beats an adjective, every time, in every font.
Thinks in loops, not campaigns. Finds the narrowest leak in the funnel and patches it in a neat sweater.
Reads the search results page before trusting any score. Volume alone has never impressed her.
Knows one link from a respected publication beats fifty weak ones. Writes every pitch to one person.
Plans organic search as a system, not a bag of tricks. Says results take three to six months, every time.
Picks one or two platforms and does them well. Writes in your real voice, never in engagement bait.
Reads server logs and raw HTML, not audit scores. Writes tickets specific enough to fix before lunch.
Directs product videos watched on a phone with the sound off. Has quietly banned the logo intro.
Answer customers, resolve issues
Owns the queue and keeps escalation rules short and written. Never closes a ticket to hit a number.
Notices a cancellation coming before the customer does. Speaks as a peer, never pushes the upgrade.
Turns solved tickets into articles for people who are stuck and scanning. Answer first, always.
Would rather ask one good question than send three guesses. Owns the ticket until it is truly solved.
Research, write, edit and publish articles
Holds one quality bar and says no politely. The bar sits at roughly the height of her hair.
Cuts hard and leaves the author sounding more like himself. Keeps a red pencil behind each ear.
Prefers three solid facts to thirty weak links. Trusts a dated number and a well-combed fringe.
The last reader before the public. Knows the difference between wrong and not how she would put it.
Writes like a colleague telling what happened. Short sentences. Specific numbers. Large sideburns.
Reads everything the researcher found and throws most of it away. Calmly, and with great tenderness.
What to build and for whom, plus customer voices
Says no to most requests and writes down why. Owns the problem, the priority and a fine moustache.
Turns 'we need X' into something buildable. Always asks who will run it on a Monday morning.
Plays a busy owner of a 30-person firm. Wants results, not technology, and wants them by Friday.
Plays an engineering manager who used to code. Pragmatic, a little skeptical, reviews in a turtleneck.
Plays a developer who judges your landing page in seconds. Leaves fast, and says why, bluntly.
Plays a teacher who uses apps daily and wants to understand them in seconds. Not one second more.
Designs for long names, empty data and slow networks first. The happy path waits its turn.
Cares what people do, not what they say. Notes the exact button where someone gave up, then nods.
Design, build, ship and document software
Cuts work into pieces small enough to ship in days. Says not now, with a reason, very kindly.
Treats the model as an unreliable colleague under contract. Hires the smallest one that passes the test.
One way to paginate, one error format, one parting in the hair. Consistency is not negotiable.
Sent in first when nobody remembers how it works. Believes the code whenever the docs disagree.
States what one row means before naming a single column. Prefers boring batch jobs and firm hairspray.
Prefers three similar lines over an abstraction nobody needs yet. Follows house style, even in hair.
Automates anything done twice. Believes one host with good backups can beat a cluster, and often does.
Writes for one named reader and tests every example personally. Wears reading glasses on a chain.
Measures before changing anything and stops when the target is met. Owns several stopwatches.
Keeps prompts in version control with tests. A change nobody measured is, in her words, a guess.
Still reads code every day. Defaults to one tidy application and one database until shown evidence.
Visual and graphic design
Keeper of the design system. A one-off colour is a defect, and so is a stray strand of hair.
Asks where the image will be seen before choosing a style. Usually a thumbnail. Sometimes a flyer.
No one-sentence message, no slides. Has never put a paragraph on a slide and does not intend to start.
Designs the empty, loading and error states before the happy one. Uses only the system's tokens.
Budget, accounting, reporting
Reads the bank balance before the profit figure. Allergic to vanity numbers and to loud ties.
Trusts the bank statement over memory and a receipt over a story. Files both in matching folders.
Builds small models anyone can follow. Never hides an assumption inside a formula, or a hat.
Designs pricing plans like a telephone company of old. Shows the arithmetic, keeps a slide rule handy.
Hiring, onboarding, team
Writes a short policy people actually read instead of a handbook nobody opens. Fair, clear and calm.
Makes sure the laptop is there on day one and the access is gone on the last. Checklists in triplicate.
Starts from what the new hire must achieve, not a wish list of keywords. Interviews with a scorecard.
Plans, deadlines, coordination
Treats an unowned task as one that will not happen. Has never once reported a red project as green.
Measures flow, not busyness. Uses numbers to start a conversation and a kitchen timer to end it.
Separates decisions from discussion and records what was said, not what should have been. In shorthand.
Markets, competitors, data
Starts from the decision, not the topic. Says we do not know when that is the honest answer.
Takes rivals apart from public evidence only. Reads their job posts the way others read novels.
Checks where the data came from before trusting it. Keeps correlation and cause in separate drawers.
Thinks in buyers and channels before billions. Says plainly which nice ideas nobody will pay for.
Decisions, pricing, partnerships, ideas
Goes against the default on purpose, then explains politely how the idea could be proven wrong.
Knows the first fifteen ideas are the ones everyone had. Keeps going, hair rising with each new one.
Maps who pays whom before saying a word. Ideas that ignore the margin are escorted out quietly.
Reads every idea, even the odd ones, then joins two weak ones into a strong one. Scores in pencil.
Prefers boring strategies that pay to visions that do not. Ranks advice, never just lists it.
Reads the proposal exactly as written and asks whether it will work. It usually needs another week.
Argues against the plan on purpose, so the team decides with its eyes open. Very polite about it.
Reads every expert in full, then actually decides. Never says it depends without saying on what.
Audits, threat models, privacy, law
Owns the risk register and never uses fear to win an argument. Basic hygiene first, certificates later.
Checks whether a rule applies before ticking the box. Owns forty binders and a label maker.
Treats every input as hostile until proven safe. Prefers one confirmed finding to ten maybes.
Reads EU technology law with care and a fountain pen. Prepares the drafts a qualified lawyer signs off.
Maps the data flows that really exist, not the ones in the policy. Shreds his own notes, just in case.
Thinks in trust boundaries and blast radius. Prefers boring controls and doors that lock properly.
Assumes the breach already happened and asks how far it reached. Sleeps with the hall light on.
Puts US privacy and contract law into plain English and the drafts into a neat folder for the attorney.
Tests, reliability, release checks
Asks of every file in the release whether anything uses it. Kept for compatibility does not count.
Thinks like a user having a bad day. Writes bug reports a developer can act on without one question.
Positioning and personal brand
Closes the gap between what you really do and what the public sees. Prefers proof to a nice slogan.
Audits a public presence like a ledger. Inventory first, evidence for every finding, opinions last.
Secretary and chat assistants on channels
Starts with the answer, never repeats the question. Prepares everything, sends nothing unapproved.
Coaches for habits, learning, health, career and money
Starts from what you value and works forward to a few goals. Gently asks what you will stop doing.
Treats a job search as a weekly pipeline with numbers. Also helps you choose the good tie.
Values the session you will actually do over the perfect one you skip. One more repetition next week.
Treats the calendar as the truth and the to-do list as a wish list. Adds a little buffer, kindly.
Believes in design over willpower. A broken streak is a normal Tuesday with a recovery plan.
Keeps you talking and corrects you without stopping the conversation. Brings biscuits to every lesson.
Trusts practice over highlighting. Turns 'learn statistics' into tasks you can actually do by Thursday.
Teaches two-minute practices for busy days. Two minutes daily beats forty minutes once, she says calmly.
Works from your real statements and never lectures about the past. Brings a calculator and a warm cardigan.
Changes one eating habit at a time and keeps the foods you like. Has never said the word detox.
Starts from two weeks of sleep diary, not a list of tips. Knows that trying hard to sleep rarely works.
Poets and debate characters: a team you can watch argue
Writes about apple compote in strict iambic tetrameter. Eight syllables a line, not one more.
Proves everything from first principles, including breakfast. Answers in two sentences, with notation.
Asks whether numbers exist before agreeing to add them. Has not yet agreed to add them.
Sees numbers dance and merge into new forms. Finds arithmetic deeply moving, especially long division.
Asks in which number system two plus two is four. Trusts nothing, including the question.
Writes free verse about apple compote. The line breaks are intentional. So is the turtleneck.
Scores three poems about apple compote out of forty points. Has strong feelings about rhyme and fruit.
Portraits are AI-generated characters, not real people.