fisser.ai is a management consulting practice focused on IT strategy and employee AI enablement — helping European SMBs and scale-ups (20–2,000 people) transform how their technology functions operate and how their people use AI. Starting 1 September 2026 with an anchor client already confirmed, the practice launches with a fully automated client acquisition system: four inbound and outbound funnels, an Apollo-enriched lead pipeline, Claude-powered personalisation, and Xolo handling all invoicing — all running on a systems stack of ~€276/month (Phase 1), scaling to ~€366/month from Phase 2.
The first phase focuses on proving the model at day rate, before shifting to project-based pricing from early 2027 — removing weekly capacity constraints and targeting a first full-year run rate of €150k–€180k. By 2028, with the first subcontractor onboarded and the LinkedIn authority flywheel spinning, the target is €300k+ in total firm billings, with a first FTE hired via EOR in the DACH market and the firm operating as a multi-market European practice.
How it all fits together
How paying clients are acquired and grown
LinkedIn outreach
3 tracks — followers, leads, hiring signals
Website inbound
fisser.ai lead capture
Networking events
QR card → booking
Panel speaking
QR on stage → leads
n8n + Apollo + Claude quality filter
Decision makers only reach your calendar · exec brief auto-generated before every call
Google Calendar booking
2–3 calls/day · 3 days/week · fully prepared
Xolo.io — invoice sent automatically
Fatturazione elettronica · recurring billing · expense tracking
Pricing model evolution
Phase 1 (Sep–Dec 2026): day rate €800/day anchor client. Phase 2+ (Jan 2027): project pricing at €1,500/day equivalent. Advisory day rate €900 available from Phase 2 for ad hoc days only.
How authority and following are built
Why this matters for everything else
When someone gets your business card, they check your LinkedIn. When a cold outreach lands, they look at your profile before responding. When an event organiser considers a speaker, they check follower count. A strong following makes every funnel convert better.
Where you are and what's next
From freelancer to Business Director
The shift this enables
You stop being capped at your own hours. fisser.ai becomes a practice. You take the client relationship and strategy. Subcontractors deliver at €900/day (you keep €300–500 margin). Income compounds across multiple clients.
The hire roadmap
Select a funnel
3 tracks
High volumeInbound
High qualityEvents + cards
Highest qualityPanels + trade shows
Max influenceLinkedIn — three campaigns running in parallel
Track 1 — follower growth (broad)
IT managers, HR leads, Ops directors, project managers, team leads. Algorithm fuel. 30–40 connections/day, warm generic note.
Dux-Soup Campaign AAny company sizeTrack 2 — lead generation (decision makers only)
Founders, CEOs, COOs, CTOs, Chiefs of Staff at 20–2,000 person European companies. Apollo-filtered, personalised sequences per role. 10–15/day.
Dux-Soup Campaign BApollo-filtered20–2,000 employeesTrack 3 — consulting-to-hire (job signal targeting)
Apollo monitors companies hiring for AI/IT strategy roles. Finds decision maker (not recruiter). Message: "Saw you're hiring for Head of AI — I could help assess the setup and get the team ready before they arrive." 5–10/day.
Dux-Soup Campaign CApollo job filterDaily refresh45–65
Total connections/day
20–35%
Acceptance rate
4–8 wks
To first lead result
Website — fisser.ai inbound funnel
Speaks to pain not credentials. Two entry points: book a 30-minute call, or download a free AI readiness checklist. Apollo Insights de-anonymises visitors — n8n catches companies who visited without converting.
Form submitted or call booked
n8n webhook fires. Lead object created.
fisser.ai webhookn8nApollo enriches + Claude scores
Company size, funding, industry pulled. Claude scores 1–10 and routes.
Apollo APIClaude APIPersonalised response within 5 minutes
High scores: calendar link. Mid: 3-email nurture. All from your Gmail.
Claude APIGmailApollo Insights — anonymous visitor recovery
Companies visiting without converting identified. Claude writes warm outreach.
Apollo Insightsn8n1–3%
Visit to booking
High
Self-selected quality
2–4 mo
To meaningful volume
Networking events
Business card with QR code (or link from business card) links to Google Calendar. Scan triggers n8n — Apollo enriches, Claude scores, personalised confirmation sent before you leave the room.
QR scanned or link opened
n8n fires on new Calendar event. Name, email, title captured.
Google Calendarn8nApollo enriches + confirmation sent
Claude writes personalised confirmation immediately.
Apollo APIClaude APIGmailPre-call brief 24hrs before
Company context, likely pain, pitch angle, suggested questions.
Claude APIGmailLow
Volume
Very high
Quality
Immediate
First result
Target events
Milan Digital Week · Web Summit · Slush Helsinki · NOAH Berlin · TNW Amsterdam · VC portfolio events
Panel speaking
Goal is for organisers to request you. At 2,500 followers with strong AI content, organisers start noticing. QR on screen links to bento.me — LinkedIn, website, booking in one tap.
Build credibility (months 1–4)
Post consistently on AI topics. Engage event organisers on LinkedIn. At 2,500 followers pitch proactively.
Pitch + curate content
Claude helps draft talk structure. 3–5 slides max. Closing slide with prominent QR. Repurpose into 3–5 LinkedIn posts.
Present — QR visible throughout
QR on closing slide, mention during talk, visible for full Q&A.
QR scans → same automated pipeline
n8n fires, Apollo enriches, Claude scores, confirmation within minutes.
100–500
Reach per slot
Max
Influence signal
4–6 mo
To first slot
Target events
AI Week Milan · VivaTech Paris · DLD Munich · AI Summit London · TNW Amsterdam · World Summit AI · Bits & Pretzels Munich
Pre-launch sprint
Jul – Aug 2026 · Systems build phase
Week in the life
Mon–Thu
Full-time at 1KOMMA5°
June: legal appointments
Jul–Aug: system building async
Friday (Jul–Aug)
1 early BD consultation call
CRM review (10 min)
LinkedIn content scheduled
Weekend build day
Sat or Sun — 1 day only
~6–8 weekends total
Each weekend = 1 system live
Pre-requisites — June 2026 (complete before July 1)
These Italian legal and identity steps happen in June before the systems build. Goal: Partita IVA active, business bank account open, digital identity established — every July subscription is licensed cleanly to the business from day one.
Register with Anagrafe (Milan)
Formalise Italian residency at Milan municipality — required for all Italian government services and to open a Partita IVA as a resident.
Activate SPID (digital identity)
Italy's national digital identity — needed to access Agenzia delle Entrate, INPS, and all government portals. Activates at a post office, CAF, or authorised provider with your passport.
Set up PEC (certified email)
Legally equivalent to registered mail. Required for Partita IVA registration and all official communications. ~€5–10/year via Aruba or Infocert.
Obtain Firma Digitale (digital signature)
Legally sign contracts and official docs electronically. Bundle with PEC at the same provider — Aruba offers both together for ~€30/year.
Open Partita IVA (end June)
Register as a freelancer with Agenzia delle Entrate, ATECO code 70.20.09 (management consulting). Your commercialista submits the form — takes 24–48hrs to activate.
Update Revolut personal address to Milan
Update residential address in the Revolut app to your Italian address. Keeps your existing account active and EU-compliant post-move.
Open Revolut Business account
Separate business account for all subscriptions and invoicing. Requires Partita IVA to register as a business. Italian IBAN available — connect to Xolo.
Get Italian SIM + business phone plan
SIM-only plan registered to Partita IVA. Sign after Partita IVA is open so it is correctly expensed as a business cost (50% deductible).
Set up Xolo.io account
Connect Partita IVA, configure fatturazione elettronica, link Revolut Business IBAN. Pre-configure 1KOMMA5° as a recurring client ready to auto-invoice from 1 Sep.
Enrol in SSN at ATS Milano
Register for Italian public health at ATS Milano, Via Statuto 5 or Corso Italia 19. Bring Partita IVA, codice fiscale, and passport. Assigns your Medico di Base.
Notify German Finanzamt of move
Inform German tax authority of change of residence to Italy. Coordinate with your commercialista and a German Steuerberater on timing to avoid dual tax residency overlap.
July–August 2026 — Systems build (start July 1, ordered)
The goal is to build a highly autonomous growth engine before the anchor client starts — so that all funnels are actively prospecting, the pipeline is warming, and the BD system runs without daily manual effort. By 1 September every lead source, automation flow, and client-facing touchpoint is live. Tools built with Claude; tools.fisser.ai hosted on Cloudflare Pages with Google SSO so you sign in with your Google Workspace account. fisser.ai website also built with Claude as a separate project to keep context clean.
Deploy tools.fisser.ai (GitHub + Cloudflare Pages + Google SSO)
Create fisser-tools GitHub repo, connect to Cloudflare Pages, point tools.fisser.ai subdomain. Add Google OAuth so all tools require sign-in with your Google Workspace account. Everything else deploys here.
Build fisser.ai website with Claude
Single-page lead capture site built with Claude (separate Claude project for shared context). Pain-focused copy, Google Calendar booking embed, AI readiness checklist lead magnet, Apollo Insights script for visitor de-anonymisation.
Set up bento.me link page
One-tap link hub: LinkedIn, fisser.ai, Google Calendar booking. This is the QR destination for business cards and panel slides — must be live before cards are ordered.
Order business cards with QR code
Card front: name, Business Director, fisser.ai, email. Back: QR linking to bento.me + "Book a free 30-minute call". Order via Moo.com — 100 cards, ~€40.
Configure Google Calendar booking page
Set 3 days/week availability, 2–3 slots/day. Add intake question: "What's your main challenge?". This is the conversion endpoint for every funnel — must be live before any outreach starts.
Set up n8n cloud + core workflows
Create n8n cloud account. Build lead pipeline: webhook → Apollo enrichment → Claude scoring → Gmail outreach → Linear issue created. Also build: post-call form trigger → Claude summary → Linear issue comment posted → follow-up email sent.
Set up Apollo.io + 3 prospect lists
Configure Track 1 (IT/HR/Ops, any size), Track 2 (C-level 20–2,000 EU), Track 3 (companies hiring AI/IT roles). Install Apollo Insights script on fisser.ai for visitor de-anonymisation.
Set up Linear (free tier) — 3 projects
Create 3 projects: (1) fisser.ai Initiatives — internal builds and strategy work, each system becomes an issue. (2) Customers — one issue per client, custom workflow: Lead → Future Opportunity → Offer → In-Project → Closed. Call transcripts auto-posted as comments via n8n. (3) Customer Initiatives — sub-projects per client engagement (e.g. 1KOMMA5° AI Enablement Platform). Configure n8n webhook to auto-create a Customer issue when a lead scores 7+ in the pipeline.
Configure Dux-Soup Turbo + 3 campaigns
Campaign A: follower growth (broad). Campaign B: lead gen (decision makers). Campaign C: job signal targeting. Connect Dux-Soup webhooks to n8n. Set daily limits: A=35/day, B=12/day, C=8/day.
Set up Google Sheets (lightweight data log only)
Create master lead sheet with columns: Name, Email, Title, Company, Source, Score, Status, Next Action, Call Date, Notes, Track. n8n writes automatically — this is the source of truth until the client widget replaces it.
Start LinkedIn content rhythm
Post 3–4x/week from July 1 using fisser-weekly tool for draft generation. Both Dux-Soup tracks running. Goal: 1,600–1,800 followers by September 1.
Configure Xolo recurring invoice for 1KOMMA5°
Set up auto-invoice to fire on September 1 for the first monthly retainer. Test the full Xolo → SDI → client notification flow. Confirm with commercialista that setup is correct.
Phase 1 — Anchor client + proof of concept
Sep – Dec 2026 · 4 months
Week in the life
Mon–Thu (~32 hrs)
Client delivery (1KOMMA5°)
LinkedIn post or engage daily
3 campaigns autonomous
Daily (~8 hrs total)
CRM review (10 min)
1–2 pre-qualified BD calls
Post-call notes (2 min)
Log expenses in Xolo
Digest review Friday
Phase 1 systems setup (Sep–Dec 2026)
Pre-launch systems are already live and generating pipeline. Phase 1 completes the call intelligence layer — making BD calls more effective — and builds the client pipeline widget mid-phase once the BD rhythm is established. These are the tools that make every client interaction more efficient and more trackable.
Enable Google Meet transcription
In Google Workspace Admin → Meet safety settings → enable Transcripts. Saves .docx to Drive after every call. Replaces manual post-call note entry entirely.
Build n8n transcript → CRM flow
n8n Drive trigger watches for new Meet transcripts → sends to Claude API for structured extraction (pain points, next steps, signals) → posts structured comment on Linear Customer issue → drafts and sends follow-up email via Gmail.
Build real-time call term helper
Single HTML tool at tools.fisser.ai/calls (built with Claude). Web Speech API listens during calls, Claude surfaces plain-English definitions of technical terms + smart follow-up questions on your second screen.
Set up Wispr Flow
System-wide voice dictation for Mac + iPhone (~€12/mo). Used for post-call notes on non-Meet calls, LinkedIn draft adjustments, strategy thoughts. Fallback input layer when automation cannot capture.
Build client widget — tools.fisser.ai/clients (mid Phase 1)
Client pipeline tracker built with Claude showing each client from discovery through engagement, invoicing, and renewal. Pre-fills from Linear Customer issues. Linear remains the source of truth — this widget is a read view on top of it.
Tune Apollo + Dux-Soup based on live data
After 6–8 weeks: review which company sizes, roles, and message angles are converting. Adjust Apollo filters and Dux-Soup templates. This is the first iteration — expect to tune monthly from here.
Phase 2 — Stabilisation + pricing shift
Jan – May 2027 · 5 months
Week in the life
Heavy delivery week
~28–32 hrs project work
BD distributed daily
Light delivery week
~12–16 hrs project work
BD calls daily (2–3)
Every Friday
Pipeline digest (15 min)
Xolo: expenses + invoices
Phase 3 — First subcontractor
Jun 2027 · pivot point
Phase 4 — Validate the model
Jul – Dec 2027
Phase 5 — First FTE hire
Early 2028 · if model validated
Phase 6 — Multi-market expansion
2028–2029+
Architecture principle
All tools are either fully autonomous or require under 5 minutes of daily input. Apollo and Dux-Soup handle outbound prospecting. n8n connects everything. Claude handles all intelligence. Linear is the source of truth for all client relationships. Xolo handles all finance. Google Meet + Gemini handles call transcription. Wispr Flow accelerates all voice input across the system.
Core automation layer
Finance layer
Google Workspace backbone
Input acceleration
Client-facing presence + infrastructure
Total costs
~€276/mo
Phase 1 stack
~€366/mo
Phase 2+ (+ Sales Nav)
€0
Web hosting
100%
Fully expensable
All four acquisition funnels feed into the same n8n backbone. The only manual inputs are: checking off tasks in the weekly tool, posting LinkedIn content, and dropping 2-minute post-call notes (or letting Meet transcription handle it automatically).
Lead pipeline — all funnels unified
Lead enters from any funnel
LinkedIn accept (Dux-Soup webhook) · website form · Calendar booking via QR · Apollo Insights visitor ID. Source tagged automatically.
n8n normalises → Apollo API enriches
Company size, funding stage, industry, headcount. Track 3 also passes job role being hired for.
Claude scores 1–10 and routes
7+: Linear Customer issue created automatically + personalised email with calendar link within 5 minutes. 4–6: 3-email nurture over 7 days. Below 4: logged only. Subcontractor candidates flagged to separate Linear label.
Call booked → exec brief generated
24hrs before: Claude writes company context, likely pain, recommended pitch angle, 2–3 suggested questions. Auto-sent to Gmail.
Post-call → automated follow-up
Meet transcript auto-processed OR Wispr Flow dictates into Google Form. Claude extracts structured data → Linear Customer issue updated with call summary comment → follow-up email sent. Linear is the permanent record.
Client confirmed → Xolo invoices
Recurring clients auto-invoiced 1st of month. Project milestones raised manually (2 min). Fattura elettronica sent to SDI automatically.
LinkedIn content engine (runs in parallel)
Monday: Claude scans AI/IT news + drafts posts
3 post angle suggestions based on recent trends delivered to Gmail. 4 full post drafts in fisser-weekly tool ready to personalise.
You review + Wispr dictates adjustments
Use Wispr Flow to voice-dictate personalisation directly into the post text field. 5 minutes total.
Post + engage (20 min daily)
3 Dux-Soup campaigns running autonomously in background throughout the day.
Weekly rhythm (fisser-weekly tool)
Monday: Generate this week
Claude reads phase context + full task history → builds focused 6-task list with step-by-step detail. LinkedIn post drafts generated simultaneously.
Through the week: check off tasks
Each task has step-by-step how-to. Skip what won't happen — carries forward automatically. Storage persists between sessions.
Friday: Run review → feeds next week
Claude analyses completions, writes honest assessment, surfaces next week priorities. Nothing forgotten or repeated unnecessarily.
Two-layer call intelligence — Linear as the record of truth
Layer 1 is post-call: Meet transcribes automatically, Claude extracts structured data, and three things happen in parallel — the Linear Customer issue is updated with a structured call summary (the permanent record), Google Sheets is updated as the data log, and a follow-up email is sent. Layer 2 is real-time: a browser tool surfaces plain-English definitions of technical terms as they come up during the call.
Layer 1 — post-call automation
Meet transcription enabled
Google Workspace Admin → Meet safety settings → enable Transcripts. Saves .docx automatically to "Meet Recordings" folder in Drive after every call. No manual action needed.
n8n Drive trigger fires on new transcript
n8n watches the Meet Recordings folder. When a new .docx appears, the post-call workflow fires automatically within seconds of the call ending.
Claude extracts structured data
n8n sends transcript to Claude API: "Extract as JSON — lead name, company, pain points (array), budget signals (array), objections (array), agreed next steps (array), follow-up angle, suggested status change." Returns clean structured data in ~5 seconds.
Linear Customer issue updated — permanent record
n8n finds the matching Customer issue in Linear by company name → posts a structured comment: call date, pain points, budget signals, objections, agreed next steps. If signals are strong, issue status is automatically advanced (e.g. Lead → Future Opportunity). This becomes the authoritative history of the relationship — visible when writing proposals, briefing subcontractors, or reviewing a client's journey.
Linear issue becomes the source of truth
The issue comment thread is now the permanent, structured record of the relationship. Every subsequent n8n workflow — exec brief generation, proposal drafting, subcontractor handover — reads the Linear issue comment thread via the Linear API and passes it to Claude as context. No spreadsheet needed.
Follow-up email drafted and sent
Claude writes a personalised follow-up referencing their specific pain points and agreed next steps. n8n sends via Gmail. Both outputs (Linear comment + email) happen in parallel — total time from call end to follow-up sent: under 5 minutes.
Wispr Flow fallback for non-Meet calls
For Zoom, phone, or in-person calls: immediately after, dictate notes into the Google Form using Wispr (~2 minutes speaking). n8n picks up the form submission and runs the same flow — Linear issue updated with call summary, follow-up email sent.
Why Linear is the right place for call history
Every time you open a client's Linear issue you see the full relationship history — every call summarised, every pain point mentioned, how their thinking evolved. When you win the project, the briefing document for a subcontractor is already half-written. When you review clients at end of phase, you have the data. Linear's issue + comment structure is built for exactly this kind of longitudinal record. Claude can read the full comment thread at any point — before the next call, when writing a proposal, when briefing a subcontractor.
Layer 2 — real-time term helper (during the call)
How it works — no extra cost
A single HTML file uses the browser's free Web Speech API to listen to your microphone. Every 30 seconds it sends the latest chunk to Claude API: "Identify any technical terms or acronyms. For each give: 1-sentence plain-English definition + one smart follow-up question." Results appear in a clean panel on your second screen or iPad. No Fireflies, no Otter, no extra subscription.
Open on second screen before the call
tools.fisser.ai/calls — open in Chrome or Edge. Click "Start listening." Allow microphone permission.
During the call — terms surface automatically
Technical terms picked up as the client speaks. Definitions panel updates every 30 seconds silently. Shows: term + plain-English definition + suggested follow-up question.
After the call — raw transcript available as backup
Full session transcript saved. If Meet transcription failed or call was on another platform, this feeds into the Wispr fallback flow for the Layer 1 post-call processing.
Wispr Flow — where it fits across the full call workflow
Before: Dictate prep thoughts into exec brief doc. During: No role — real-time term tool handles it. After Meet: Fully automated — transcript → Linear issue updated → follow-up email sent. After other calls: Wispr into Google Form (2 min) → same automated flow. Between calls: Dictate LinkedIn ideas, client thoughts, strategy notes into any active tool.
Recommended: Cloudflare Pages — free forever
All fisser.ai internal tools are static HTML files. No server, no backend, no database. Claude API calls happen client-side from the browser. Cloudflare Pages hosts everything for free — you already use Cloudflare for fisser.ai DNS, so setup is one click. Domain cost is the €80/year (€6.67/month) you're already paying.
Internal tools structure at tools.fisser.ai
Full cost breakdown
Licensing begins July 2026 once Italian bank account is set up. One advisory day at €900 covers the full Phase 1 stack 3× over. Everything 100% expensable against your Partita IVA.