Co-founder & CMO, Reqbeat
Co-founder seat · 10–25% equity · Equal say · Fully remote, async, your own hours
A co-founder seat, not a job. You'd own a real share of Reqbeat and have an equal voice on where it goes. Like any founder of a bootstrapped company before revenue, there's no salary: you share in revenue from day one and in the company as your equity vests. You can keep your current job or client work while it ramps. Details under The deal.
1
What Reqbeat does
Reqbeat tells you when a company opens a role that means it needs what you sell, and drops that company straight into your outbound.
- The signal: a real job posting. Most come from public job boards; some come straight from applicant tracking systems like Greenhouse, Lever and Ashby.
- Who it's for: GTM engineers, agencies running outbound for clients, recruiters, and any B2B team for which "they just opened a role for X" means "they need us now."
- How it fits your stack: save a search (role, skill, country, company type, seniority) and new matches arrive where you already work: a Clay template, an n8n workflow, an Apify actor, a webhook or a Claude Code skill pack. There's also an API and an MCP server if you'd rather wire it up yourself.
- Typical play: push newly hiring companies into an existing Instantly, Lemlist or HeyReach campaign, so they hear from you the week they start hiring.
- Pricing: self-serve. Free to start, usage-based after that, no sales calls.
2
Where we are
Built, not launched. Over the last month we shipped a Claude Code skill pack, an n8n workflow, a Clay template, an Apify actor, a dozen playbook pages and listings in the main MCP directories.
Zero users so far. We never sent a launch post or a single outreach message. No external usage, no paying customers. Engineering was never the bottleneck; GTM was.
3
Why it might be worth your time
- The hard part is built. Data pipeline, API, MCP server, webhooks and metered billing are live. You'd market a product, not a roadmap.
- Growth is cheap to serve. Each new customer costs almost nothing, so revenue turns into profit fast.
- Your equity stays yours. Bootstrapped by choice: no investors, no board, no plans to raise. No dilution, nobody else's timeline.
- Nobody owns this audience yet. GTM engineering is a new job, and agents are starting to call data APIs directly. How this crowd buys signal data is still being decided.
4
The role
Get Reqbeat its first real users, then its first paying ones, by doing the work yourself.
This is a hands-on seat, not a strategy or advisory one. There's no marketing team to delegate to: you write the copy, ship the landing pages, send the onboarding emails, post in the communities and run the experiments. Engineering builds whatever growth needs, usually within a day.
- Activation first, reach second. If people who find us don't make a first call, more traffic won't help. You own the path from landing page to first useful match in their Clay table or n8n flow, then getting people onto it.
- The audience is still open. Our working bet is GTM engineers, technical founders and automation people who wire their own outbound in Clay, n8n or Claude Code, and are user, buyer and budget in one. If the evidence points elsewhere, we follow it.
- You set growth priorities. You decide what gets built for growth, and engineering ships it.
- Budget: close to zero until there's revenue. Paid acquisition comes after paying customers.
What your first weeks might look like: rewrite the landing page and first onboarding email; build a Clay or n8n play on Reqbeat and get it in front of your first prospects; talk to the first ten people who sign up; fix what stopped the ones who didn't get a first match.
5
Who you'd work with
- Founder & engineer. 25 years in software. Built the data pipeline, API, MCP server, watches and billing; ships most changes within a day. Based in Norway.
- Stephen, CEO. Based in Sweden.
6
How we work
- Keep your paying work while it ramps. This can fit around a job or client work. No fixed hours, no on-call, no schedule. Freelance GTM work is fine as long as it doesn't compete with Reqbeat; client work in Clay or n8n will probably make you better at this.
- Results, not hours. Work from anywhere, whenever suits you.
- Async by default. Ideally one short call a week, and as few others as possible.
7
What you bring
A head start: at least one of these two, ideally both.
- A trusted audience in the GTM engineering crowd that you can post to on day one: a newsletter, a LinkedIn or X following, a YouTube channel, or a known presence in communities like Clay's or n8n's. Real engagement matters more than follower count.
- Zero to paying, without a following. You've personally taken a product from zero to its first paying customers when nobody knew who you were, and can say exactly what moved the numbers: outbound, communities, content, partnerships, whatever it was.
And all of these:
- Hands-on GTM engineering, in practice: you've built Clay tables and n8n workflows yourself, and wired up webhooks and APIs. MCP and Apify are a plus.
- You make the things yourself: copy, landing pages, onboarding emails, community posts, experiments.
- Fluent English and comfortable working mostly async.
Nice to have: experience with self-serve or product-led products, or having sold to GTM engineers or outbound agencies before.
8
The deal
A co-founder seat: ownership and an equal say. No salary and no fixed hours.
- Equity: 10–25% of the company, vesting over four years with a twelve-month cliff.
- Say: an equal voice on where Reqbeat goes from day one.
- Revenue share: 30% of all Reqbeat revenue from day one, while your equity vests, so you earn well before any exit.
- First 3 months: our shared goal is €10,000 MRR. Your 30% of that is €3,000 a month, and it grows with the company. In week one we agree the leading indicators we'll track together on the way there (signups, first matches, first paying customers).
- What you build stays yours: if we part ways for any reason, you keep your 30% share of revenue from every customer you brought in for 12 months afterwards. Content you publish under your own name, and your audience, stay yours. All of this is in writing before you start.
Right for you if you're confident you can get a product to real revenue fast, and you'd rather earn a share of what you build and own part of the company than take a salary.
Not right if you need a guaranteed income, or you'd rather direct the strategy than do the work.
9
How to apply
Reply with your CV or LinkedIn and short answers to these three questions. A few sentences each is plenty.
- Runway. There's no salary while we ramp up. Can you cover yourself for the first few months with a job, client work or savings? A yes is enough.
- Your head start. Do you bring an audience in the GTM engineering crowd, experience taking a product from zero to paying customers without one, or both? Give us a few specifics:
- Audience: where you post, rough size, and one post or campaign that got people to try something.
- Zero to paying: the product, what you did yourself, and how many paying customers you got in how long.
- Your 90-day plan. How would you get Reqbeat to €10,000 MRR in 90 days? An outline is fine: where the first ten users come from, and where the revenue comes from.
Optional bonus: start free on Reqbeat, set up a watch, and tell us what confused you.