Oki

What do they actually do

Oki aggregates a company’s existing work signals (code commits, tickets, Slack, docs) into a single, clickable progress report for leaders. It highlights what’s shipping, what’s slipping, and where blockers or overloaded contributors exist, with every insight linked back to the original source for context Oki homepage YC launch.

Teams connect tools like Slack, GitHub/GitLab, Jira, Docs, and Notion; Oki auto‑groups activity by teams or projects and generates periodic updates (they reference daily and weekly formats) that leaders can drill into via timelines, messages, and commits Oki homepage YC launch. The product is self‑serve with an option to book demos, and it markets enterprise readiness (SOC 2 Type II, HIPAA, encryption at rest/in transit, on‑prem options, and a no‑training‑on‑customer‑data policy) Oki homepage.

Who are their target customer(s)

• CTO / VP of Engineering: No single, reliable view of what’s shipping vs. blocked; wastes hours chasing status across tickets, commits, and Slack. Needs automated aggregation with links back to sources for quick verification.
• Founder / CEO (early-stage): Wants a short, trusted daily/weekly briefing that flags high‑risk work and blockers without reading threads and PRs. Needs a fast way to spot issues requiring escalation YC launch.
• Engineering Manager / Team Lead: Struggles to detect overloaded contributors and blocked tickets early; manual triage and reallocation are time‑consuming. Needs team‑level signals tied to underlying messages and commits Oki homepage.
• Product Manager / Head of Product: Can’t easily tie roadmap milestones to actual engineering activity, causing misalignment on priorities and delivery dates. Needs multi‑source reports linking execution back to plans Oki homepage.
• Security/IT or Compliance Lead (larger orgs): Concerned about sensitive data flowing to external AI services; needs encryption, on‑prem/VPC options, and attestations (SOC 2, HIPAA) to pass procurement Oki homepage.

How would they acquire their first 10, 50, and 100 customers

• First 10: Hand‑sell via warm networks (YC founders, investor/founder intros). Run white‑glove pilots where the team connects core tools and delivers the first report highlighting concrete blockers and slippages, then collect feedback and mini case studies YC launch.
• First 50: Tighten the self‑serve funnel and integration listings; publish short how‑to demos/templates. Do targeted outbound to CTOs/VPs via LinkedIn and engineering Slack communities, and offer referral credits to existing customers Oki homepage.
• First 100: Adopt a hybrid motion with a small AE/SDR pod to close larger pilots. Ship a reproducible onboarding playbook and security pack (SOC 2, HIPAA, on‑prem/data handling docs) to shorten procurement, and add 1–2 channel partners (consultancies/platforms) to resell/embed Oki Oki homepage.

What is the rough total addressable market

Top-down context:

Oki sits at the intersection of project management and team collaboration software. Public estimates put project‑management software at roughly $6.6B (2022 base) and team collaboration at about $21.8B (2023), implying a combined, conservative scope around $25–30B today Grand View Research Fortune Business Insights.

Bottom-up calculation:

Global developers total roughly 27–29M; assuming 1 leader for every 8–12 developers yields ~2–3.5M direct buyer seats (CTOs/VPs/EMs/PMs) Evans Data Statista. At $500–$2,000 per leader per year, that suggests a $1–7B engineering‑leader SAM, with upside as Oki expands to other functions.

Assumptions:

• Leader-to-developer ratio averages 1:8 to 1:12 across org sizes.
• Annual price per leader license ranges from $500 to $2,000 depending on features/deployment.
• Adoption initially concentrates in engineering leadership, expanding to other functions over time.

Who are some of their notable competitors

• Atlassian Jira: The dominant issue and project tracking tool for software teams; deep workflows and reporting. Oki differs by auto‑aggregating signals across tools and generating source‑cited leadership updates.
• Asana: Cross‑functional work management and reporting used by software and business teams. Oki aims to ingest across engineering systems and Slack/docs to create leader‑ready briefings.
• Linear: Modern issue tracking and project planning popular with startups for speed and UX. Oki positions itself as an overlay that stitches multiple sources into progress summaries.
• Jellyfish: Engineering management platform focused on aligning engineering work with business priorities and spend. Oki overlaps on leadership visibility but emphasizes cross‑source, source‑linked updates.
• LinearB: Developer analytics and delivery optimization (DORA metrics, workflow automation). Oki overlaps on status and blockers but centers on narrative progress reports tied to underlying artifacts.