Sako (Co-founder)Product DesignVisual & Branding

Building a $9K MRR Design Subscription from $0

How I co-founded Sako, shipped the full product stack (Next.js + NestJS + AI automation), cold called 700 prospects, closed 2 clients, and learned why productized agencies don't scale — all on a $500 budget.

$500

Total Budget

$9K

MRR Closed

700+

Cold Calls Made

Case study visual
Built withNext.jsNestJSStripeLangGraphn8nAI AutomationCold OutboundPricing StrategyGTMDesign SubscriptionB2B SaaSBrandingLive site

Context

The working context

Team

KV

CO-FOUNDER, HEAD OF PRODUCT & GTM

Koushik Venkatesan
GS

CO-FOUNDER, CLIENT RELATIONSHIPS

Gowri Shankar Sanjay
BS

HR & FREELANCE HIRING

Bhavna Sruthi
AS

ACCOUNT EXECUTIVE

Ashwath S
PA
JK
KK

AI CONSULTANT

Khushal Kindra

Overview

Jun 2025 – May 2026 · 1 year Sako was a B2B design subscription service for SaaS companies between $500K–$10M ARR. The pitch: ship landing pages, pitch decks, and motion assets in 48 hours — no hiring, no contracts, just production-ready work. I co-founded Sako with Gowri Shankar and built the entire product and GTM stack from scratch: product (marketing site, client app, studio app, API, AI design generator), GTM (cold outbound workflows, AI-powered lead enrichment, email sequences, 170+ SEO-optimized blog posts), sales (cold called 700+ prospects in Q1 2026, closed 2 clients worth $4,500/month each = $9K MRR), and operations (pricing, unit economics, capacity planning, SLA tracking, 7-person freelance team). All of this was built on a $500 budget using AI-assisted coding, no-code automation, and scrappy execution. Why I left: Productized agencies are hard to scale without raising capital. The team pivoted to video editing (not my thing), so I decided to take what I learned and apply it inside a company with distribution.

My expertise

Product design, full-stack development, GTM strategy, cold outbound, pricing & unit economics, AI automation, no-code workflows, team management, design subscription operations

Problem

What needed to change

How do you build a B2B design subscription service — product, GTM, outbound, pricing, operations — from scratch, with no funding, no existing audience, and a $500 budget?

In June 2025, my co-founder Gowri and I decided to start Sako. The hypothesis: B2B SaaS companies between $500K–$10M ARR need design help, but they can't afford full-time designers and agencies are too slow and expensive.

We wanted to build a productized design service: fixed monthly price ($2,500–$8,500/month), 48-hour delivery SLA, unlimited revisions, design + motion in one subscription.

But we had: No funding (bootstrapped with $500 for domain + Stripe setup + hosting). No existing audience (had to cold call from scratch). No agency background (neither of us had run a service business before). No technical infrastructure (had to build the product from scratch).

The challenge: Build a company that delivers production-ready design in 48 hours, competes with agencies without their overhead, closes clients with no warm intros or brand, and operates profitably with a team of 7 freelancers — while also building the product, designing the brand, writing 42 pages of marketing content, running cold outbound, and managing the team.

Questions we had to answer

01

What is a productized design service and why is it hard to scale?

02

How do you price a design subscription service?

03

What does '48-hour delivery SLA' actually mean operationally?

04

How do you build a product stack on a $500 budget?

05

How do you cold call 700 people and close 2 clients with no warm intros?

06

Why did you leave if you had $9K MRR and clients loved the work?

$500

Total Budget

Total capital deployed (domain, Stripe, hosting, initial tools)

$9K

MRR Closed

2 clients at $4,500/month each

700+

Cold Calls (Q1 2026)

Cold outbound to B2B SaaS founders and marketing leads

7 freelancers

Team Size

2 co-founders + 5 freelance contractors

170+

Blog Posts

AI-assisted SEO content automation

4

Apps Shipped

Marketing site, client app, studio app, API

42

Pages Designed

Marketing site + internal dashboards + pitch decks

17

Email Campaigns

Outbound email sequences via Brevo with 18–59% open rates

Alignment

What success had to look like

Success criteria

Success wasn't about becoming a $10M ARR company. It was about proving the hypothesis: Can you build a design subscription service that delivers better work than agencies, operates profitably without VC funding, closes clients even with no warm intros, and does all of this while building repeatable GTM systems?

We defined success as: Ship the product (4 apps). Close 2+ clients. Deliver on the 48-hour SLA. Build repeatable GTM systems. Stay profitable.

We hit all of these. The reason I left wasn't failure — it was realizing that productized agencies hit a ceiling unless you raise capital or pivot the model (which the team did by moving to video editing).

Design themes

Speed Over Perfection

Ship fast, iterate based on client feedback. The first version doesn't need to be perfect — it just needs to work.

AI as a Force Multiplier

Use AI to automate content (blog posts, email sequences, lead enrichment), but keep humans in the loop for quality control.

Scrappy Execution Over Big Budgets

$500 budget means no paid ads, no expensive tools, no agency hires. Everything had to be built or automated in-house.

Systems Over Heroics

Don't manually do everything. Build workflows, automation, and repeatable processes so the team can scale without you being the bottleneck.

Process

01Vision & Brand Identity
02Build the Product (4 Apps)
03Write the Marketing Site (42 Pages)
04Build Cold Outbound Workflows
05Cold Call 700 Prospects
06Close First 2 Clients ($9K MRR)
07Deliver on 48-Hour SLA
08Automate SEO (170+ Blog Posts)
09Realize Productized Agencies Don't Scale
10Walk Away (Team Pivots, I Find Next Chapter)

Constraints

The tradeoffs we had to work inside

01

$500 budget — no paid ads, no expensive tools

Every dollar mattered. Couldn't afford Webflow, couldn't afford paid ads, couldn't afford design agencies. Everything had to be built or automated in-house.

02

No existing audience — cold call from scratch

No warm intros, no case studies, no brand recognition. Every client conversation started from zero trust.

03

48-hour delivery SLA — operationally brutal

Promising 48-hour delivery means the entire team has to be coordinated. One delay breaks the SLA.

04

Team of 7 freelancers — no full-time employees

Everyone was contract-based. Coordination was async. Had to build systems to keep everyone aligned.

05

No technical co-founder — I had to learn full-stack dev while building

Came from design/motion background. Had to learn Next.js, NestJS, Stripe webhooks, LangGraph, n8n — all while running the business.

06

Productized agency ceiling — hard to scale without capital

Productized agencies max out around $500K–$1M ARR unless you raise capital to scale the team.

Behaviors encouraged

  • Subscribe to a design subscription (monthly recurring)
  • Submit briefs and trust the 48-hour SLA
  • Refer other SaaS companies (word-of-mouth growth)
  • Use Composer (AI design generator for landing pages)

Behaviors discouraged

  • Hire full-time designers (too expensive, too slow to ramp)
  • Use agencies (too slow, too expensive, too inconsistent)
  • Build design in-house without systems (chaotic, unscalable)

Process

How the work moved from messy to shipped

Building Sako was a masterclass in scrappy execution — shipping a full product stack, designing the brand, writing all the content, and closing real clients, all on a $500 budget over 12 months. Here's the story from first sketch to exit.

01

Phase 1: Vision, Brand Identity & Logo Brainstorm

Before writing a single line of code, I needed to answer: what does Sako look like? The name 'Sako' came from a brainstorm session — it needed to feel sharp, fast, and B2B credible.

Brand decisions: Logo — green abstract 'S' mark (symbolizes speed, flow, systems). Colors — Neon green (#9AE83E) + purple gradient + dark mode default. Typography — Switzer Variable (clean, modern, B2B SaaS aesthetic). Spacing — 4-point system. Components — buttons, avatars, image placeholders, link styles.

Created a full branding guideline doc in Figma for the team to stay consistent across every surface — product, marketing, decks, social.

Logo Brainstorm & Exploration

Initial logo exploration and brainstorming sessions

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Sako Design System & Branding Guidelines

Full design system: logo, colors, typography, spacing, components

02

Phase 2: Landing Page Prototype (Before trysako.com Existed)

Before writing a single line of code, I designed the full landing page in Figma. This prototype validated the visual direction, the narrative structure, and the product story before committing to development.

The prototype established: hero section with the 48-hour SLA promise front and center, 'how it works' flow (submit → draft → review → ship), pricing table with 5 plans, and FAQ that pre-handles objections.

This prototype was used in early sales conversations before the live site was ready — and it closed the first demo calls.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Landing Page Prototype (Pre-Launch)

Landing page prototype designed in Figma before trysako.com existed

03

Phase 3: Building 4 Apps on a $500 Budget

I shipped the full Sako product stack in 3 months using AI-assisted coding (Cursor, v0, Claude). Four apps, one budget, zero compromises on product quality.

Marketing site (trysako.com): 42 pages of MDX content, Figma → Next.js (Tailwind, Framer Motion), OG image generation, sitemap, JSON-LD for SEO.

Client app (app.trysako.com): Dashboard for submitting briefs, tracking tasks, managing brands, Stripe billing integration (checkout, subscriptions, webhooks), review board for asset feedback.

Studio app (studio.trysako.com): Admin kanban for task management, client overview (active clients, MRR, capacity tracking), AI insights (task estimation, complexity scoring).

API (api.trysako.com): NestJS backend (PostgreSQL via Supabase), Stripe webhooks, task workflows, SLA tracking, Composer Gateway (SSO for AI design generator). Total cost: $500.

Tech stack: Next.js 16, NestJS, Clerk (auth), Stripe, Supabase (PostgreSQL), PostHog (analytics), Railway + Vercel (hosting). React 19, TypeScript, Tailwind CSS 4, shadcn/ui, Framer Motion.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Client App Prototype

Sako client dashboard — brief submission, task tracking, brand management, review board

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Studio (Admin) App Prototype

Sako studio — kanban, capacity tracking, client management, AI task insights

trysako.com — Live Marketing Site

Live marketing site — 42 pages of content, full brand, built in Next.js

Pricing Page

5-tier pricing from Composer Free ($0) to Enterprise ($8,500+/month)

Product Page

Product page — Sako OS, 48-hour SLA explainer, feature breakdown

Sako Launch Video

Official Sako launch video

04

Phase 4: Composer — AI Landing Page Generator (LangGraph + OpenRouter)

I built Composer: an AI-powered landing page generator for Sako clients. The idea — give users a free AI tool, then upsell them to the human pod when they need higher quality.

What it does: Generates landing page copy + layout using LangGraph multi-agent workflows. Routes through OpenRouter (GPT-4, Claude, Gemini). Includes ClaimsOS — a compliance/claims validation system that checks if AI-generated copy makes unsupported claims. 'Send to Sako' button hands AI drafts to the human pod for polishing.

Tech stack: Next.js 16, TypeScript, Tailwind 4, LangGraph 1.x for multi-agent orchestration, Vercel AI SDK 6.x for streaming, Supabase (auth + database), Trigger.dev for background jobs, Bun runtime.

Lesson: PLG doesn't work for productized services. Clients wanted human quality from Day 1, not AI drafts. Composer was discontinued — the human pod was always the real differentiator.

05

Phase 5: AI-Powered Outbound Workflows (n8n + LangGraph)

I built a self-hosted n8n instance (n8n.sako.agency on Railway) to automate the entire cold outbound machine — from lead capture to email delivery to Slack-based approvals.

Workflows built: (1) Lead capture + enrichment — Apollo, Clearbit webhooks. (2) ICP scoring — LangGraph agents score leads based on company size, tech stack, and hiring signals. (3) Email sequences — Brevo drip campaigns, warm-open tracking, follow-up triggers. (4) Slack command center — /sako commands for approvals, metrics, workflow actions. (5) Analytics — weekly growth reports. (6) PR outreach — hook generation, tracking.

Integrations: Apollo (sequencing, contact data), HubSpot (lifecycle tracking), Resend/Brevo (email infrastructure), OpenAI/Anthropic/Google (LLM APIs for enrichment). Neon PostgreSQL 17 as the automation database.

Brevo campaign results (17 campaigns total): Peak open rate: 59.49% (EU - Sako, Jan 2026). Consistent open rates: 18–25% across Feb/Mar 2026 campaigns. ~600 recipients per campaign by Feb 2026. Total outbound sequences: January through March 2026.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Sample Cold Email (Meme-Based)

One of the outbound email formats — meme-based cold email that drove above-average open rates

06

Phase 6: Pricing, Unit Economics & US + India Entity Registration

I designed Sako's pricing strategy and unit economics from scratch — no playbook, just first-principles thinking about what the market would pay and what we could deliver profitably.

Plans: Composer Free ($0/month, AI only), Composer Pro ($30/month, AI + 100 credits), Core ($2,500/month, 1 active task, design + motion, 48h SLA), Ops Base ($4,500/month, 2 active tasks), Enterprise ($8,500+/month, 3+ tasks + strategy).

Unit economics (Core plan): Revenue: $2,500/month. Cost of delivery (freelancer fees, tools, overhead): ~$1,200/month. Gross margin: ~48%. Key insight: productized agencies need 50%+ gross margins to scale profitably.

Entity registration: Registered Sako in the US (Newark, Delaware) via Stripe Atlas to unlock Stripe's full feature set and US payment rails. Also registered a Pvt. Ltd. in Chennai, India, to handle freelancer payments legally. Two entities, one product, $500 total budget.

Pricing Page — Live

5-tier pricing designed to capture PLG-adjacent users and convert them to human pod subscriptions

07

Phase 7: Cold Calling 700 Prospects & Closing $9K MRR

I personally cold called 700+ B2B SaaS founders and marketing leads in Q1 2026. No SDRs. No warm intros. Just me, a list, and a pitch.

Process: Sourced leads from Apollo, LinkedIn Sales Navigator, and manual research. Built a list of 700 companies (B2B SaaS, $500K–$10M ARR, hiring for design/marketing roles). Called every single one. Pitched Sako's 48-hour SLA. Booked 15+ demos. Closed 2 clients at $4,500/month each = $9K MRR.

Conversion rate: ~0.3% (2 closed / 700 calls). Not great in isolation — but enough to validate the offering. The ones who said yes loved the 48-hour SLA. Speed was the real differentiator.

The pitch deck that closed clients: Designed the client pitch deck in Figma. Every slide was optimized to answer the first objection before it was asked — why not an agency, why not in-house, why now.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Client Pitch Deck

The pitch deck used to close both $4,500/month clients

08

Phase 8: Delivering on the 48-Hour SLA (Managing a Team of 7)

The 48-hour SLA was the core promise of Sako. Making it work with a team of 7 remote freelancers required systems, not heroics.

Task workflow: QUEUED → IN_PROGRESS → IN_REVIEW → COMPLETED. SLA timer starts when brief is marked 'Ready' — scope clear, assets provided, one approver assigned. SLA pauses if client delays feedback.

Tools: Studio app (kanban, capacity tracking), Slack (real-time notifications), Review board (in-app asset feedback with annotations), PostHog (product analytics), Resend (email notifications).

Result: Hit the SLA ~85% of the time. Misses were usually client-side delays (late feedback, missing assets). Built SLA tracking directly into the product so clients could see exactly where their task was — and why it might be delayed.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Studio App Prototype

Studio admin app showing kanban, capacity tracking, and client management

09

Phase 9: Automating SEO — 170+ Blog Posts

With no budget for paid ads, SEO was the only scalable acquisition channel. I automated 170+ blog posts using AI content generation workflows.

Process: Keyword research (manual + Ahrefs). LangGraph workflows for content generation (GPT-4 + Claude). Automated publishing via Sanity CMS. Internal linking, meta descriptions, OG images. Topics: design ops, productized services, landing page best practices, SaaS marketing.

Result: 170+ posts published in 3 months (Nov 2025 – Jan 2026). Organic traffic: 0 → 500 sessions/month. The blog became the top acquisition channel after cold outbound.

Sako Blog — 170+ Posts

AI-automated blog with 170+ SEO-optimized posts published in 3 months

10

Phase 10: SMM Content & Social Brand Presence

Beyond the product and outbound, I designed Sako's social media presence — visual content that carried the brand into LinkedIn and Twitter feeds.

The SMM content used the same design system as the product — neon green, Switzer Variable, dark mode — so every post felt like an extension of the brand, not a disconnected social team output.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

SMM Content Posts

Social media content designed for Sako's LinkedIn and Twitter presence

11

Phase 11: Running 17 Email Campaigns (18–25% Open Rates)

I ran 17 cold outbound email campaigns from Jan–Mar 2026 using Brevo (email infrastructure) + Apollo (contact data). Total recipients across all campaigns: 6,000+.

Campaign strategy: Segmented by geography (US, EU, APAC). A/B tested subject lines on most campaigns. Sent 2–3x per week to different segments.

Best-performing campaigns: (1) EU - Sako (Jan 20): 59.49% open rate, 2.08% CTR, 98 recipients — tight targeting + regional relevance. (2) US - Sako (Jan 20): 36.67% open, 0% CTR, 106 recipients — opens were strong but CTA didn't convert. (3) Feb Outbound 3 (Feb 13): 22.72% open, 1.89% CTR (highest click rate), 480 recipients — 'Book a Fit Check' CTA was the winner. (4) Feb Outbound 9 (Feb 27): 21.64% open, 1.49% CTR, 609 recipients.

Average metrics across all 17 campaigns: Open rate: 18–25% (industry average for cold B2B is 15–20% — we were above average). Click rate: 0.5–1.9% (industry average is 2–3% — slightly below, needed better CTAs). Unsubscribe rate: 0.17–1.28% (low = messaging resonated).

Key insight: Cold email builds awareness, but it's not a closer. The real conversions came from the email → call → demo → close sequence. Email warmed people up; the call closed them.

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Sample Cold Email (Meme-Based)

One of the outbound email formats — meme-based cold email that drove above-average open rates

12

Phase 12: GA4 Traffic Analysis — Where 2,488 Users Actually Came From

I tracked all traffic to trysako.com using GA4 (Jan–May 2026). 2,488 active users. 2,486 new users — nearly 100% cold audience, zero brand recognition at the start.

Traffic sources: Brevo email (1,617 users, 65% of all traffic). Direct/typed URL (739 users, 30% — brand recall from cold calls). Organic Google (26 users — SEO just starting after 170+ blog posts). Google CPC (18 users, $100 test budget). LinkedIn referral (8 users).

Top landing pages by active users: (1) Homepage — 1,344 users, 10,800+ views. (2) Fit Check booking page — 779 users, 1,129 views (strong demo intent). (3) Pricing page — 271 users, 337 views (bottom-funnel). (4) ROI Calculator — 146 users, 201 views (highest intent signal, 29.7% bounce rate — lowest on the site).

Bounce rates told the real story: Homepage 51.3% (half engaged). Pricing 39.6% (60% went deeper — strong signal). ROI Calculator 29.7% (highest intent — should have used this as the primary CTA in emails). Product page 23.2% (users who got here were deeply engaged).

Geographic distribution (top cities): Ashburn VA (373, likely AWS infra traffic), Singapore (193), Chennai (104), Melbourne (113), Sydney/Canberra (216 combined). Australia was surprisingly strong — APAC SaaS market responded well.

Key learnings: Email drove 65% of traffic, but only 31% of visitors reached the booking page. The ROI Calculator had the lowest bounce rate — should have promoted it as the primary email CTA instead of 'Book a Demo'. SEO needed 6+ months to compound (only 26 organic users after 3 months of blogging). Direct traffic (739 users) = brand recall from cold calls — people heard the name, then typed it in.

Takeaways

What changed once the work met reality

What didn't go as planned

01

$500 budget means no margin for error

Every tool, every hire, every expense mattered. Used free tiers aggressively (Vercel, Railway, Supabase), AI-assisted coding (Cursor, v0, Claude), and no-code tools. Spent money only on essentials. What I learned: you don't need a big budget to build a product. You need time, focus, and the ability to learn fast.

02

Cold calling 700 people is brutal

I personally cold called 700+ B2B SaaS prospects in Q1 2026. Most said 'not interested.' Some hung up. Conversion rate: ~0.3%. But that was enough to validate the offering. What I learned: cold calling works if you have the stomach for it. But it doesn't scale without SDRs or automation.

03

48-hour SLA is operationally brutal

Promising 48-hour delivery means one delay breaks the chain. Built SLA tracking into the product (timer starts when brief is 'Ready,' pauses if client delays). What I learned: SLAs are a forcing function for operational discipline. But they only work if clients hold up their end.

04

Productized agencies hit a ceiling without capital

By March 2026, we'd maxed out at $9K MRR. To scale further, we'd need to hire full-time designers, build a sales team, and invest in paid marketing — all requiring capital. I chose not to raise. The team pivoted to video editing. I decided to take what I learned and apply it inside a company with distribution.

05

Email open rates were strong (18–25%), but clicks didn't convert to booked calls at scale

Sent 17 email campaigns to 6,000+ recipients. Open rates above industry average, but click rates below (0.5–1.9% vs. 2–3% benchmark). Even when people clicked, only 15 demos actually booked out of 779 booking page visitors (1.9% booking conversion). Lesson: cold email is top-of-funnel, not a closer. The winning sequence was email → call → demo → close. Email warmed people up; the call is what got them on a video.

What shipped

Built 4 Apps on a $500 Budget

Shipped the full Sako product stack (marketing site, client app, studio app, API) in 3 months using AI-assisted coding and scrappy execution. Next.js 16, NestJS, Stripe, Supabase, Clerk — all on free and starter tiers.

4

Apps shipped

$500

Total budget

42

Pages designed

Live Marketing Site

trysako.com — the live product built on $500

Closed $9K MRR with Cold Call + Email Follow-Up Combo

Ran a multi-touch outbound strategy: 17 email campaigns (6,000+ recipients, 18–25% open rate) → cold calls (700+ in Q1 2026) → personalized follow-ups to people who opened but didn't click → demos (15 booked) → close.

The winning combo: Send cold email → Wait 2 days → Call if they opened but didn't click → Reference the email on the call ('I sent you a note about Sako's 48-hour SLA — did you get a chance to look?'). This combo had a higher booking rate than email-only or call-only. Both closed clients came from the email → call → demo → close sequence.

17 campaigns, 6,000+ recipients

Cold emails sent

18–25% (above B2B average of 15–20%)

Email open rate

700+ in Q1 2026

Cold calls made

15

Demos booked

2 ($4,500/month each)

Clients closed

$9K

MRR achieved

Figma assets may take 1–2 minutes to load from CDN. Please wait if you see a blank or loading frame.

Client Pitch Deck

The deck used to close both $4,500/month clients

Automated 170+ SEO Posts & Hit 18–59% Email Open Rates

Built LangGraph workflows to automate blog content generation. Published 170+ posts in 3 months. Ran 17 outbound email campaigns through Brevo with consistent 18–25% open rates and a peak of 59.49% on the EU segment launch.

170+

Blog posts published

0 → 500 sessions/month

Organic traffic growth

17 (peak 59.49% open rate)

Email campaigns

Blog — 170+ Posts

AI-automated Sako blog

Delivered on 48-Hour SLA (~85% Hit Rate)

Managed a team of 7 freelancers to deliver landing pages, decks, and motion assets within 48 hours. Built SLA tracking, capacity planning, and async coordination tools into the Studio app.

~85%

SLA hit rate

7 freelancers

Team managed

QUEUED → IN_PROGRESS → IN_REVIEW → COMPLETED

Task workflow stages

Built AI-Powered Outbound Workflows (n8n + LangGraph)

Automated lead enrichment, ICP scoring, email sequences, and Slack-based approvals using self-hosted n8n + LangGraph multi-agent workflows. Registered both US and India entities to handle payments on both sides.

Lead capture, enrichment, sequencing, analytics, PR outreach

Automation workflows built

Apollo, HubSpot, Brevo, Slack, OpenAI, Anthropic, Google

Integrations

US (Stripe Atlas, Delaware) + India (Pvt. Ltd., Chennai)

Entity registrations

Outcome

What shipped and what it proved

$500

Total Budget

Total capital deployed — domain, Stripe, hosting, initial tools

$9K

MRR Closed

2 clients at $4,500/month each

700+

Cold Calls Made

Q1 2026 outbound volume — personally dialed

4

Apps Shipped

Marketing site, client app, studio app, API — all production-grade

170+

Blog Posts Published

AI-automated SEO content in 3 months

7 freelancers

Team Managed

2 co-founders + 5 contractors, fully remote, async

~85%

SLA Hit Rate

48-hour delivery on eligible tasks

42

Pages Designed

Full marketing site content designed and written

2,488

Total Active Users (GA4)

GA4-tracked users across trysako.com (Jan–May 2026)

10,800+

Total Page Views

Homepage alone (Sako | Design Ops for B2B SaaS)

1,030

Pricing Page Views

337 active users viewed pricing — strong purchase intent signal

591

ROI Calculator Views

201 active users — lowest bounce rate (29.7%), highest intent page

1,129 views

Fit Check Bookings Page

779 active users viewed the Cal.com booking page — strong demo intent

Brevo email

Top Traffic Source

1,617 users (65% of all traffic) came from cold outbound emails

17

Email Campaigns Sent

Jan–Mar 2026 outbound blitz via Brevo

18–25%

Email Open Rate

Above industry average (benchmark: 15–20%) across Feb/Mar campaigns

59.49%

Peak Email Open Rate

EU - Sako campaign (Jan 20, 2026) — tight regional targeting worked

0 → 500 sessions/mo

Organic Traffic Growth

3-month SEO ramp from zero (170+ blog posts published)

39.6%

Pricing Page Bounce Rate

60% of pricing visitors engaged further — strong bottom-funnel signal

What came next

I walked away from Sako in May 2026, but I don't regret it. I proved I could build a product from scratch, close clients with cold outbound, manage a remote team, design pricing and unit economics, and automate GTM — all on a $500 budget. Key learnings: 1. You don't need a big budget to build a product. You need time, focus, and AI-assisted coding. 2. Cold calling works, but it's brutal. 700 calls → 2 clients is a 0.3% conversion rate. That's normal. 3. Productized agencies hit a ceiling. You max out around $500K–$1M ARR without raising capital. 4. SLAs are a forcing function for operational discipline. But they only work if clients hold up their end. 5. I'd rather be the operator inside a company with distribution. Building Sako taught me I'm great at systems, GTM, and execution — but I don't want to be the founder who has to fundraise to scale. What's next: Taking everything I learned at Sako and applying it inside a company that already has distribution, capital, and a GTM engine. I want to be the operator who builds the systems — not the founder who has to raise money to scale them.

2026 — Kelashik.