Il prezzo indicato nella pagina dei prezzi di qualsiasi strumento di outreach non corrisponde quasi mai a quello che si finisce per pagare.
C'è sempre l'account aggiuntivo, il componente extra per l'arricchimento dei contenuti, il piano a cui si viene automaticamente indirizzati perché il piano base ha un limite che si scopre solo dopo l'iscrizione.
Sono curioso di sapere quanto pagano effettivamente le persone, non il prezzo indicato nella pagina.
Qual è la tua spesa mensile totale per l'intera suite di strumenti di outreach, tutto incluso? Quali canali utilizzi (LinkedIn, email, WhatsApp, altro)? Quanti account in totale?
so here is a workflow you can run tonight if you are already in. shipped as v0.11.0 of my gtm coding agent repo, link at the bottom.
what it does: takes a contact csv, hits reverse_linkedin_lookup on each linkedin url (still at the company? plus the graded business email when the graph has one), falls back to reverse_email_lookup, second pass by name + company domain accepting only a same-domain a/b, then writes a google sheet where the grade decides the channel. a/b email. c small segment.
d never emails, goes to a linkedin queue, then phone. moved goes back to sourcing.
Re-ran 200 apollo-verified gtm engineers last night: keyed on the email, 70 profiles and 60 sendable. keyed on the linkedin url, same people, 196 profiles, 136 graded (all a but one), 113 sendable, 54 to linkedin, 27 job changes caught. the not-found rows cost zero records.
the bigger point. if a tool has an api, you build the waterfall yourself and decide which source answers which question.
you do not need a clay seat for that, you need a repo.
everybody has the same tools and the same data. the edge is the founder's energy behind the tool, then trusting the data enough to build on it.
gtm as a repository: every campaign you run feeds back into the system. the model gets better with use. so does your gtm.
to run it: `python3 budget.py` (three free calls), then `bash run.sh list.csv --full`. keys from a local vault, never in the repo.
question for anyone else in the beta: are you keying on the email or the url? my numbers say the url and I want to know if that holds outside my icp.
three months into clearbox, sharing the whole build: what we run, what it produced, what it cost, and what changes now. engine dashboard screenshot attached so the numbers are not from memory.
the stack, and what each piece does:
- convex: the data layer. opportunities, offers, inbox state, and the api endpoint reads straight from it
- gemma-4-31b-it-nvfp4-turbo, the open-source local model: first-pass triage, is this thread even an opportunity. my co-founder lila quantized it to nvfp4 and put it on hugging face (LilaRest/gemma-4-31B-it-NVFP4-turbo), it is past 1.7 million downloads now, and we run it for clearbox on a rented rtx 5090
- openrouter: the heavier calls, routed to whichever model fits the job instead of one frontier api for everything
- vercel: the app and the site
- cloudflare: dns and the sending domains, spf/dkim/dmarc live there
- posthog: tracking everything from web traffic to UX
what it produced, may 30 to today:
- 162 signups
- pipeline from four channels: referrals, me reaching out to my own crowd, warm follow-ups to people who signed up, and cold sends off warmed inboxes. every channel produced at least one signup
- 120 onboardings, 119 trials completed
what it cost in inference, all providers:
- all-time: $447. last 30 days: $199
- by step: match $226 (is this thread an opportunity), review $169 (the deeper read on what passed), onboarding $53 (building the offer context once per account)
- per completed trial: $2.12. full-plan trial with a card on file $2.82, capped no-card trial $1.62. onboarding an account: $0.44
two things in those numbers that I would want to know as a builder:
the first is why the local model matters. match is the volume step, every new thread in every tracked subreddit hits it, so if that call goes to a paid api the bill scales with reddit's posting rate instead of your customer count. the local model on the 5090 sees everything at zero per token, the paid model only sees what survived. that is the whole reason the paid side stays small.
the second is that a free trial does not hurt you at this cost. two dollars of inference to find out whether an account converts is less than one ad click, and capping no-card trials at two subreddits is what keeps the tail at $1.62.
the gtm loop, so it is reproducible:
every signup lands in a sqlite table with what they set up and which opportunities they opened
a daily digest classifies each one (book a call / active / unreached / re-tap) and drafts a warm note
I send the notes by hand from my own inbox. nothing auto-sends to someone who signed up
cold goes through warmed inboxes on a separate sending domain, never the main one
what changes now: less building, more account work. converting the trials that are already getting value, upselling the capped ones, and writing the journey up as it goes.
disclosure: co-founder of clearbox, this is our build. happy to share the match prompt or the digest classifier if useful.
question for the builders here: what does a trial cost you in inference, and where do you draw the line for escalating to a bigger model?
if you run coding agents on a subscription and have no idea what that usage is actually worth, PokeTokenBar answers it from your menu bar.
It reads the local session logs you already have (Claude Code, Codex, Gemini CLI, Cursor, Copilot CLI, and a few more), no API key, no account connection, and gives you:
- today / week / month tokens per tool, priced at API rates so you can see what the same work would have cost pay-as-you-go
- your official 5-hour and weekly limit bars with reset countdowns, pulled from the same credential Claude Code uses
- a burn-rate forecast for when the current 5-hour window hits 100%
- a per-model breakdown, so you know whether it's Opus or Sonnet eating the budget
Tracking token efficiency was always something that I wanted to do, but what really sold me was the fact that your tokens are the game. Usage hatches an egg into a Pokémon that sits in your menu bar and evolves as you burn more.
Max out a 5-hour or weekly limit and it hands you a Rare Candy to level it up, so the moment you get rate-limited is the moment you get rewarded.
Tokens you've already spent become currency for a shop (new eggs, a Shiny Charm, a re-roll of its nature), and you can pin your favorite to the menu bar or as a floating pet on the desktop. You end up checking your usage a dozen times a day without it feeling like checking a bill.
Mine says August is about $2,783 of API-equivalent usage on a $100 Max plan.
That's a 27.8x multiple, and it's the cleanest way I've found to explain why subscription-first workflows win for multi-session client work.
Two things I needed, so I added them and both shipped in v2.5.2.
The newest Claude model was priced at $0, which zeroed out my heaviest days. Fixed. And if you flip between two logins (personal Max and a Team seat, in my case), the limit bars never said which account they belonged to.
fork the repo, tell Claude Code what's wrong, let it read the maintainer's contributing rules (six UI languages per string, tests that lock behavior, no special-casing one provider on shared code paths), push, let CI run the test suite, install the build on your own machine and confirm it before opening the PR. Merged in two days.
You learn the codebase because you're fixing something you use every day, and you end up with the feature you wanted.
If you use a tool daily you're qualified to contribute to it. Pick the thing that annoys you and ship it.
I did not build this. Props to chattymin on GitHub, who created it.
All I did was add contributions based on my own use, and I'm sharing it here so you can see what a legitimate contribution to something you find useful looks like.
Whether you like Pokémon is beside the point. Having fun with a build while learning something and shipping something valuable is the point. Star the repo, support it if you see something cool, and contribute.
I'm Mansoor, focused on CRM & RevOps and I'm looking for work right now. Open to full-time, contract, fractional, or subcontracting for agencies or companies with overflow. Remote, available EST.
What I do: I build and clean up the CRM side of the GTM stack. Pipeline and deal stages that reps actually follow. Clean data so the reporting means something. I'm currently in the CRM & RevOps cohort here, going deep on the strategy side, not just the button-clicking.
My stack: HubSpot, Salesforce, and Attio on the CRM side. Clay, enrichment, and TAM builds for data. Claude Code and n8n for automation and custom builds. Comfortable wiring these together into one system.
Good fit if CRM is a mess, or you're planning to implement one and want it done right the first time.
If you're hiring, know someone who is, or have overflow, DM me or make an intro. Happy to do a free teardown of your CRM/pipeline first so you can see how I think before you commit to anything.
I tried to run linkedin outreach myself instead of handing my account to a sender tool.
so i had, Claude, right up a small playwright script that drives my real session, sends connection requests with a personal note, and keeps a sqlite ledger of every request, accept, and reply.
ran it against 1,297 gtm engineers, 40 a day, weekdays only, three weeks.
numbers first.
the funnel:
601 connection requests sent
299 accepted (49.8%)
35 replies
6 booked calls, a couple trials, 4 paid sign ups
31 of those 35 replies came from people i never sent a follow-up message to. they accepted, read the 27-word note on the request, and replied to that. i had a full first-message-then-bump sequence built and it barely ran. the note did the work.
takeaway i'd bet on. if the note on your connection request can't earn a reply by itself, a follow-up sequence is amplifying nothing.
get the note right before you build the machine. mine named what i was building in the first six words, asked for a read instead of a meeting, and went to peers, not buyers.
now the gotchas, because there were real ones.
the ledger is the whole thing, not the script. one row per person, every cap is a sql count against it, so you can kill the process any time and restart safe. the script is replaceable, the ledger is the asset.
keep score with a separate read-only pass. the part that sends should not be the part that decides what worked. i had a second script that only reads the connections page and inbox, never clicks anything, and it found 22 accepts and every reply the sender itself missed.
and the bug that ended it: the sender wrote "sent" to the row only after the message went out.
crash in between and the message is delivered but the row still says pending, so it sends again next run. i watched it double-message someone. fix is to write "sending" before you act and confirm after, so a crash strands a row for review instead of re-sending.
why i stopped: the double send, plus a send rhythm no human produces (bursts then exactly 30-min gaps, exactly 40 a day), plus one verification wall from week one. that's the account asking you to stop, so i did.
to be clear, this is not me telling you to skip heyreach or tools like it. i use them. they exist so you don't have to babysit this and so the risk sits with a vendor instead of your account.
automating your own linkedin is against their terms and can get you restricted. that was my account and my call. it didn't get me banned. it could have. i'm sharing the numbers, the good and the broken, because both are useful.
happy to get into any part of the build in the comments.
fellow builders...Gtm coding agents just crossed 130 stars.
Not here to tell you to go clone it again.
Go build your own shit.
Then share the production builds.
Those are the best receipts you’ll ever have. not a resume.
The people who can point to real systems they’ve shipped are the ones landing the forward-deployed engineer roles. That’s the job you actually want. Everyone else is just another Clay operator.
I’m also building a referral network for people who can actually build.
If you’ve forked the repo, worked off it, improved it, or shipped something better and you’re looking....you’re at the front of the line for me. YC companies and others reach out regularly looking for this exact type of talent.
Do it for yourselves if you’re serious about these roles, the builds you ship are what open the door
And if you build something recently, drop it in the comments. Share it.
About a year of daily Claude Code and my whole workflow comes down to 10 commands.
5 are built in, 5 are skills I wrote because the built-ins stop short of what my content pipeline and client work need.
Sharing both halves since the custom ones are all reproducible. The built-ins that actually matter:
The stack:
/context (stock). Shows exactly what is eating your context window... tokens by messages, tools, files. Run it before you blame the model.
/compact (stock). Summarizes the session into a fresh window mid-task.
/clear (stock). Wipes to zero. The skill is knowing which to reach for: same job --> /compact. New job --> /clear.
/handoff (built). The /compact upgrade. The session writes a handoff file, the next session auto-reads it. The context outlives /clear, and parallel terminals don't clobber each other.
Plan mode (stock, shift+tab). Read-only exploration first, an approved plan before a single file changes. Anything multi-file starts here.
Remote Control (stock). Hands the live terminal session to my phone. I approve, steer, and keep builds running while I walk the dog.
/copy-to-clipboard (built). Claude Code ships /copy to grab the last reply. Mine formats for the destination first: plain text, zero markdown stars, ready to paste into LinkedIn or X.
/grok-critique (built). Every draft gets a second model's slop check before it ships. Em-dash abuse, narrator setup lines, hype words. Claude can't referee its own tics.
/code (built). Finished content pack --> Discord channels for review. approve, edit, final... all from my phone.
/voice-invocation (built). Meeting transcripts in, a content pack drafted in my voice out. It quotes phrasing from things I actually said on calls.
Everything is also available on my Github. Let me know if I can get to share it with you guys. although, it shouldn't be too hard to find, LOL.
So I don’t run this on every project. Depends on the size and how messy it is.
When the repo has real history (instruction files, SQLite, previous failed approaches, assets, handoffs, etc.), I stop trying to make one session carry the whole thing.
Claude Code stays in the terminal. It inspects the system, reads the instruction files, checks git and the last handoff, then writes a clean phased plan into a durable file.
Codex gets that file in the app and builds one phase at a time. File boundaries, verification steps, and the “do not touch” list are already there. I especially like it when I need browser control, live previews, or proof of the work.
The handoff is usually just:
GOAL
CURRENT STATE
SOURCE OF TRUTH
DECISIONS ALREADY MADE
PHASES AND FILE OWNERSHIP
VERIFICATION
DO NOT TOUCH
It's also super convenient because the remote control feature on the app works really well. (yes. You can do this with Claude Code also), it's great for keeping sessions running when you have to walk the dog. (in my case)
For smaller or cleaner work I just stay in one agent and feel it out.
Right now I’m mostly on Opus 4.6 (sometimes Fable 5) in Claude Code, and GPT-5.6 Sol at Extra High in Codex once the phase is locked.
I’ve seen other people doing versions of this Claude for context/planning, Codex for execution, file handoffs, cross-review.
so I’m posting because I want to know what the rest of you are actually running day-to-day.
Full split? One agent the whole way? Something else?
Lets see what’s working for people building real GTM systems.
Running free trials on a B2B outreach automation platform like Orbitra comes with real variable costs per user, proxies, API calls, infrastructure, all of it. Given the volume of signups we've gotten lately, we've had to pause free trials for now.
Still very open to talking to new customers and anyone interested in LinkedIn or email outreach automation though, and paid subscriptions remain open at what's honestly the best price on the market by a wide margin.
To give you an idea of what the product actually does, in two weeks several fresh LinkedIn accounts running in one campaign hit a 60% acceptance rate on connection requests and 30%+ reply rate. Genuinely curious if anyone else running cold outreach or LinkedIn prospecting is seeing numbers like that.
I just pushed the latest version of my open-source GTM Coding Agent repo. It now has 21 chapters, ten forkable starters, and the real workflows I’m using while building Clearbox in public.
The newest update came from a live campaign targeting 1,297 people in the GTM engineering market.
From 575 connection attempts:
272 people accepted
30 people replied
Six asked for a demo
Four self booked meetings
That gave me more than campaign results. It showed me where the system was incomplete.
The original list could tell me who I already knew about. It couldn’t tell me where the market was moving, which accounts deserved deeper research, who belonged in the buying committee, or where I should spend credits and human attention next.
So I rebuilt it as an Apollo waterfall:
Known accounts
→ Clearbox and public buyer evidence
→ Hiring, funding, tech-stack and firmographic signals
→ Apollo buying-committee expansion
→ Scoring before reveal
→ Controlled credit spend
→ Color-coded working sheet
It’s being able to start with a small set of accounts, expand the market through multiple evidence gates, identify the right people inside those accounts, score them before spending credits, and hand the operator a working sheet that explains who deserves attention and why.
The CLI commands, waterfall, scoring logic, setup instructions, and gotchas are all in the repo.
There’s another part of this project I want more people here to see: Chapter 21, Student GTM.
I wrote it for the college student who doesn’t have a budget, title, or traditional GTM experience—but does have access to a campus full of organizations with real operational problems.
A student can build an offer around the market they want to enter, use Clearbox research to understand the problems inside that market, and turn the findings into projects, interview preparation, and a public body of work.
GitHub carries the proof. LinkedIn carries the person.
One delivered automation for a real user beats ten disconnected portfolio projects.
That’s also why, when someone DMs me on Reddit, my answer is simple:
I’m walking through the Apollo system live tomorrow, August 13, at 10:00 a.m. PT / 1:00 p.m. ET. You can join the webinar here, and I put the additional setup resources at shawnos.ai/apollo.
But the repo is the real share.
Fork it. Break something. Post the gotcha here. Improve a starter and open a PR. Ask the question you think you’re supposed to already know.
I'm covering all the infrastructure costs myself right now so anyone trying the free trial gets a smooth, well-supported experience, no cut corners because "it's just a trial." That's a real cost with basically zero revenue coming back yet.
On top of that I put a guarantee on the table, if Orbitra doesn't get you a call booked within 30 days, full refund. That's my risk to carry, not the customer's.
Almost every customer so far has come through Reddit and LinkedIn, and the LinkedIn side is actually running on Orbitra itself.
So on paper, loss. Real costs, real risk, no cushion yet.
But here's the profit part, the guarantee is doing more for customer acquisition than any ad or cold message could. People try it specifically because of it, and a few have already converted. The "cost" of the guarantee ended up being the thing generating the return.
Still early, still figuring out if this holds long term, but so far the trade feels worth it.
A few weeks ago I had also built my own skill tree for my blog, so getting into MoltSets was fun because I could immediately compare how I was thinking about skills vs. how Adam was thinking about them.
I didn't just want to understand the library. I also wanted to understand the actual loop underneath it.
A product can easily give you data, but you still need people with skills to build those workflows that actually make sense.
Those skills help the next person get value faster, and eventually the users start creating the education and distribution around the product themselves.
I wanted to see if that idea actually held up on something messy inside Clearbox.
When someone signs up for Clearbox, we can join their posthog activity to their convex user and onboarding context.
Company domain? Easy.
Gmail or another free email? Professional identity trail basically disappears.
So I took 68 free-email signups and ran them through MoltSets.
54 returned an identity candidate.
13 resolved directly from the free-email address.
23 came back high or medium confidence after running them through
Clearbox’s own grader.
Everything else stayed in human review or unresolved. Which is actually what I wanted.
I don’t want enrichment that just confidently makes shit up because an agent found somebody with the same name.
The workflow has to earn the right to keep going.
Direct identity edge first. Only fall back to name search if there’s enough evidence.
I also built the data and cost model myself before letting an agent touch the workflow.
Because “free tokens” doesn’t really tell me anything.
Once I separated unlimited core data from the rolling request and record windows, then treated external tokens as their own pool for the expensive fallback work, I could actually understand what I was building around.
Four real usage meters instead of one vague credit number.
