glossgo / agents
← agents/knowledge/fundingagents/knowledge/funding/PLAYBOOK.md

PLAYBOOK.md

What / Why / How Companion — 30-Day Funding Execution Plan

Author: task-decomposer (companion to cycle-1 plan) Date: 2026-04-22 (Day 1) Pairs with: agents/journal/2026-04-21_task-decomposer_funding-roadmap-30d_plan.md Source roadmap: agents/journal/2026-04-21_turkey-funding-research_glossgo-funding-roadmap.md Audience: GlossGo founder Language: English (per repo rule), Turkish proper nouns preserved.

§0 How to use this document

This is the "what/why/how" companion to the 68-task plan. The plan is the scoreboard: it has IDs, effort minutes, done-checks, and calendar dates — keep that file open for the daily checklist. This file is the coach's clipboard: every task explained in terms of business rationale (why), concrete mechanics (how), and gotchas (what breaks). Read this side-by-side with the plan. Week 1 tasks get the full deep-dive; Weeks 2–4 get compressed paragraphs because the pattern repeats. When in doubt, the plan's done-check is authoritative — this doc only explains the reasoning.

§1 Big picture — why this ordering

Front-loaded Legal/Corporate (D1–D3). Every Turkish funding channel — KOSGEB, Teknopark, TÜBİTAK BİGG, BKY angel lisans, İSTKA — accepts applications only from companies with (a) the right NACE code on Ticaret Sicil, (b) a clean borcu yoktur letter from SGK and vergi dairesi, (c) valid imza sirküleri, and (d) a submitted KOBİ Beyannamesi (KBS). These four artifacts are dependencies for everything else. If NACE is wrong, the KOSGEB submission will be rejected at the kurul stage after you have already spent 6 weeks writing the iş planı. Getting them fixed on Days 1–3 costs ~5 hours of founder time and 3–5 business days of Ticaret Sicil wait — which we run in parallel with other tracks. Delaying this by even a week cascades into Week 5 and breaks the horizon.

KOSGEB Girişimcilik Eğitimi enrollment = Day 1 / Day 2. Enrollment at kosgebakademi.gov.tr takes 15 minutes, but the allocated session may start 5–10 days later depending on demand and format (async vs sync). This is the single longest external wait on the critical path — not our work, their schedule. The 8-hour course itself is 4 modules × 2 hours spread across Week 2 and Week 3. If you enroll on D6 instead of D1, the certificate arrives after horizon end and the entire KOSGEB İleri submission (a Horizon-2 task) slips into July. This is why T07 is front-loaded even though it is a small task.

Teknopark selection deferred to Week 2 (D6). Choosing İTÜ ARI vs Teknopark İstanbul vs Bilkent Cyberpark is not a 30-minute decision — it depends on (i) whether you will physically move or stay virtual (Q10), (ii) which Ar-Ge angle you will pitch (AI matching vs dynamic pricing), (iii) which park's 2026 cohort window is closest. These inputs only crystallize after Week 1 Legal decisions settle. Making this choice on Day 1 would force you to revisit it; making it on Day 6 lets Week 1's decisions inform it.

Investor/angel outreach staggered to Week 3–4. You never send a teaser or deck before the numbers reconcile. finance-fpa delivers the investor model by D13 (T27); the deck v1 is dispatched on D16 (T51). Sending cold LinkedIn messages before the deck exists burns warm-intro paths — a BAN manager who sees a rough deck will anchor on it. Week 3–4 placement means the investor package lands in front of Galata / Arya / Keiretsu only once it is defensible. The 3 warm-intro asks in T60–T63 go out on D22 — right after deck review, before memory fades.

Deferred to Horizon-2 (next cycle, post-2026-05-20). The plan explicitly does not attempt: KOSGEB İleri actual submission (kurul window + education certificate dependency), BKY yatırımcı lisansı application (separate 6-week flow with Hazine), BİGG Stage-1 draft (needs tech co-founder decision Q4), Workup/İTÜ Çekirdek cohort applications (next open cohort after July), İSTKA çağrı monitoring (passive), EIC Accelerator (EU-level, separate pipeline). Trying to force any of these into 30 days produces half-finished submissions that get rejected — the 30-day plan is scaffolding for the submission month that follows.

§2 Day-by-day deep dive — Week 1 (Days 1–5)

Day 1 — 2026-04-22 (Wed)

T01 — Decide A.Ş. vs Ltd.Şti. going-forward structure

  • What: Write one paragraph in journal/2026-04-22_founder_entity-form-decision.md stating "A.Ş." or "Ltd.Şti." plus rationale and conversion timing.
  • Why: Ltd.Şti. is cheaper (~3K TL notary + sicil) and faster but has 50-ortak cap and requires a nev'i değişikliği (type conversion) before any priced round — angels and VCs almost always require A.Ş. for share classes, preferred rights, and ESOP. A.Ş. costs ~15K TL up front and demands a yönetim kurulu but scales cleanly through Series A. Every downstream artifact (iş planı cover page, imza sirküleri form, data room cap-table) references this decision. Deferring this past D1 blocks T05, T31–T35, and T56.
  • How:
    1. Read roadmap §11 Q1 default (keep Ltd.Şti. for 2026 grants, convert to A.Ş. pre-priced-round H2 2026).
    2. If current GlossGo is already A.Ş., you have no choice — stay A.Ş.; if Ltd.Şti., default to "stay Ltd.Şti. through 2026, convert before first angel term-sheet."
    3. Open a new file journal/2026-04-22_founder_entity-form-decision.md, write: "Entity: Ltd.Şti. · Rationale: 2026 grants (KOSGEB/Teknopark) accept Ltd.Şti.; convert to A.Ş. before priced round (target H2 2026). · Conversion cost ~25K TL + 3 weeks including new imza sirküleri."
  • Deliverable: journal/2026-04-22_founder_entity-form-decision.md (single paragraph + decision line).
  • Gotchas:
    • If you are already A.Ş., do not re-notarize anything — just log the decision and move on.
    • Do not write "undecided" or "TBD" in this file; the whole plan assumes a concrete pick. If genuinely unsure, pick the reversible default (Ltd.Şti.) and move on.

T02 — Pull current Ticaret Sicil Gazetesi PDF

  • What: Download the most recent Ticaret Sicil Gazetesi (TSG) issue that references GlossGo from ticaretsicil.gov.tr.
  • Why: The TSG PDF is the single source of truth for: company NACE code, registered address, ortaklık yapısı, sermaye miktarı, and imza sirküleri yetkililer. Every single downstream form (KOSGEB KBS, Teknopark application, BKY lisans, noter imza sirküleri, investor data room) needs this PDF. If you cannot locate it, you cannot progress Week 1 at all.
  • How:
    1. Open https://www.ticaretsicil.gov.tr in a browser.
    2. Use the "Gazete Arama" or "Sirkü Arama" page. Search by unvan (GlossGo legal name including Ltd.Şti./A.Ş. suffix) or Ticaret Sicil No if you know it.
    3. Identify the most recent issue that includes your kuruluş ilanı or any subsequent değişiklik ilanı (address, sermaye, ortak change).
    4. Download the PDF; save to outputs/legal/ticaret_sicil_gazetesi.pdf.
  • Deliverable: outputs/legal/ticaret_sicil_gazetesi.pdf, size > 0, date visible on cover.
  • Gotchas:
    • The portal sometimes returns only the index page, not the full gazette PDF. You need the full PDF that contains the actual ilan text — verify by searching the file for "GlossGo".
    • Issues older than 2023 may not be in the online archive; if missing, request a "Ticaret Sicil Gazetesi örneği" via the TOBB chamber (same request as Faaliyet Belgesi, T18).

T03 — Read NACE code field on TSG PDF; log one line

  • What: Open the TSG PDF, find the NACE line, log "NACE = <6-digit code>" in the entity-form-decision file.
  • Why: Your NACE code decides whether you are a "bilişim/yazılım" firm (J 62.xx) eligible for Teknopark vergi istisnası and KOSGEB İleri teknoloji, a "portal/platform" (J 63.12.01) also qualifying, or a "other services" (S/96.xx) which fails most tech-grant filters. T04 depends on knowing the current code.
  • How:
    1. In the PDF, locate the bullet "Faaliyet Konusu" or "NACE". The 6-digit code looks like 62.01.01, 63.12.01, 96.02.01, etc.
    2. Append to journal/2026-04-22_founder_entity-form-decision.md: NACE current: <code> plus 1-line faaliyet description.
  • Deliverable: Line appended to decision file.
  • Gotchas:
    • Some older TSGs list only the eski 4-digit sınıfsal kod, not the 6-digit NACE — in that case check MERSİS (mersis.gtb.gov.tr) logged in with e-Devlet for the canonical NACE.
    • Multiple NACE codes allowed (primary + secondary). Log the primary (first listed).

T04 — Decide NACE target code

  • What: Pick target NACE: 62.01.01 (bilgisayar programlama faaliyetleri) OR 63.12.01 (web portallarının işletilmesi). Log decision line.
  • Why: 62.01.01 is the strongest signal for KOSGEB İleri, Teknopark, and BİGG — it reads "software development" and removes any doubt about Ar-Ge eligibility. 63.12.01 is better if GlossGo's primary operation is running the marketplace portal itself rather than custom software development. Both qualify for Teknopark; 62.01.01 is the safer default. This code will be referenced on every form — picking the wrong one forces another NACE change later (another 3–5 biz day wait).
  • How:
    1. Ask: "Is the main revenue stream (a) licensing/building software or (b) operating a platform for third-party service providers?" (b) = 63.12.01; (a) or mixed leaning build = 62.01.01.
    2. GlossGo is a two-sided marketplace → 63.12.01 is technically accurate. However, if you want to preserve optionality for custom-software grants (BİGG, TÜBİTAK 1507), 62.01.01 is broader. Default recommendation: 62.01.01.
    3. Log: NACE target: 62.01.01 · Rationale: broader tech-grant eligibility, consistent with Ar-Ge hire plan.
  • Deliverable: Decision line in same file.
  • Gotchas:
    • Do not pick a secondary NACE as the primary just because it sounds fancier — primary NACE drives sigorta risk group and vergi tevkifat rules.
    • If the current code is already 62.01.01 or 63.12.01, skip T05–T06 and annotate "NACE already aligned — T05/T06 N/A" in the file.

T65 — Set up outputs/ folder tree

  • What: Create the deliverable folder tree under outputs/.
  • Why: Every task in this plan writes to a specific path. Missing parent folders cause the plan's done-checks to fail silently and you will waste time debugging "where did I put that PDF." One-time 10-min operation that saves compounded friction.
  • How:
    1. mkdir -p outputs/legal outputs/finance outputs/kosgeb outputs/teknopark outputs/investor/data_room/legal outputs/investor/data_room/cap_table outputs/investor/data_room/ip outputs/investor/data_room/metrics outputs/investor/data_room/contracts outputs/investor/data_room/misc outputs/investor/intros_sent
    2. Commit the empty folders with a .gitkeep file so the tree persists.
  • Deliverable: Folder tree exists; ls outputs/ shows all parents.
  • Gotchas:
    • outputs/ may or may not be in .gitignore — check before committing. If secrets like SGK borcu yok PDFs go into outputs/legal/, ensure the folder is not public-remote synced by accident. Default: add outputs/legal/ to .gitignore if the repo is pushed to a shared remote.

T66 — Create tracking file

  • What: journal/2026-04-21_founder_funding-status-tracker.md with columns: task ID / title / due date / status / blocker.
  • Why: Without a single status tracker, you cannot answer "what's overdue" in Friday reviews. Also required by T68 (30-day handoff note) and by future task-decomposer cycles to know what to pick up.
  • How:
    1. Create file; paste a markdown table header: | ID | Title | Due | Status | Blocker |.
    2. Copy all 68 IDs + titles from the plan §1 table. Leave status column empty; fill due dates from §3.
    3. Status vocabulary: todo / doing / blocked / done / deferred.
  • Deliverable: File with header row and 68 rows.
  • Gotchas:
    • Do not use a spreadsheet — markdown keeps it diffable in git so cycle-2 can read the delta.
    • Update daily, not weekly. 30 seconds per task completion.

T67 — Schedule weekly Friday review

  • What: Put a recurring 30-min calendar block on 5 consecutive Fridays (04-24, 05-01, 05-08, 05-15, 05-22). Note 05-01 is Labour Day — reschedule to Mon 05-04.
  • Why: A calendar commitment is the only thing that forces you to audit the tracker weekly. Skip one review and 15 tasks pile up unseen.
  • How:
    1. Open Google Calendar / Apple Calendar.
    2. Create event "GlossGo funding Friday review" 16:30–17:00, recurring every Friday for 5 weeks.
    3. In event description, paste: "Review status tracker. Mark done / blocked. List next week's batch."
  • Deliverable: 5 calendar events created (or 4 + 1 rescheduled).
  • Gotchas:
    • 05-01 (Labour Day, Resmi Tatil) — no Ticaret Sicil, no KOSGEB portal activity. Do not plan work; move review to Monday 05-04.

T22 — Decide co-founder bonus classification

  • What: Note whether any founder qualifies for KOSGEB bonus categories: kadın, 18–29 yaş, gazi, engelli.
  • Why: KOSGEB İleri grant amounts include +10% to +15% uplift for female, young, gazi founder categories. Omitting this on the iş planı costs money directly. Decision must be made before T31 (iş planı §1).
  • How:
    1. Self-assess: kadın ortak ≥25%? yaş <30? TSK emeklisi/gazi? engelli raporu?
    2. Log one line in the entity-decision file: "Bonus kategorisi: [kadın / yok / genç / gazi / engelli] — ilgili belge: [T.C. kimlik yaşı yeterli / SGK engelli raporu N°XXX]."
  • Deliverable: Line in entity-form-decision file.
  • Gotchas:
    • Do not claim a bonus you cannot document — KOSGEB audit will revoke grant and request refund with interest.
    • "Teknik ortak <30 yaş" bonuses in some KOSGEB calls require the young person to hold ≥25% ortaklık, not just be an employee.

T16 — Request SGK borcu yoktur yazısı

  • What: Pull a "SGK'ya borcu yoktur" letter via e-Devlet.
  • Why: Every Turkish grant/subsidy application requires a current (≤30 days old) SGK no-debt letter. If you have unpaid SGK primleri, the letter fails and you must clear the debt first — discovering this on D1 is much better than discovering on D25.
  • How:
    1. Go to turkiye.gov.tr → log in with e-Devlet şifresi / mobil imza / e-imza.
    2. Search "SGK borcu yoktur belgesi" or go directly to SGK hizmetleri.
    3. Select application purpose: "İhale / Teşvik / Kredi" (most grants accept this).
    4. Issue the PDF; download.
    5. Save to outputs/legal/sgk_borcu_yok.pdf.
  • Deliverable: PDF saved, date stamp within last 7 days.
  • Gotchas:
    • Mobil imza vs e-imza vs şifre: the şifre flow sometimes fails on the SGK endpoint — mobil imza (operator-issued) is more reliable. If the portal 500-errors, try again with mobil imza.
    • If you have SGK borcu (even ₺0.01), the letter prints "BORCU VARDIR" — call 170 SGK line, request detail, pay via GİB/Halkbank same day, re-request 24h later.

T17 — Request vergi borcu yoktur yazısı

  • What: Pull a "vergi borcu yoktur" letter from GİB interaktif portal.
  • Why: Same rationale as T16 — grant applications require both SGK and vergi no-debt letters. Also used by Teknopark (T38 checklist).
  • How:
    1. Open https://ivd.gib.gov.tr (İnteraktif Vergi Dairesi).
    2. Log in with şifre (TC kimlik + kullanıcı kodu) or e-Devlet.
    3. Menu: "Borç Bilgileri" → "Borcu Yoktur Belgesi" (or "Vergi Borcu Bulunmadığına Dair Belge").
    4. Issue for purpose "İhale / teşvik"; download PDF.
    5. Save to outputs/legal/vergi_borcu_yok.pdf.
  • Deliverable: PDF saved, dated.
  • Gotchas:
    • İVD farklı, GİB ana portal farklı: ivd.gib.gov.tr is the interaktif portal; intvd.gib.gov.tr is the old interactive. Use ivd.gib.gov.tr.
    • KDV beyannamesi için belirlenmiş ödeme günü geçmişse (~ayın 26'sı) borç görünebilir — ödedikten sonra 2–3 iş günü sonra sistem temizler.

Day 2 — 2026-04-23 (Thu)

T07 — Enroll in KOSGEB Girişimcilik Eğitimi

  • What: Create account on kosgebakademi.gov.tr, enroll in "Uygulamalı Girişimcilik Eğitimi" (8-hour course).
  • Why: This certificate is mandatory for the KOSGEB İleri Girişimci Programı application. Without it, the submission in Horizon-2 is blocked. Enrollment also reserves a slot — slots are first-come, and busy months (Eylül, Şubat) have 2-week waits. Early enrollment = earliest completion = room to handle re-takes if you miss a module quiz.
  • How:
    1. Browser to https://kosgebakademi.gov.tr.
    2. "Kayıt Ol" → use TC kimlik, e-posta, tel.
    3. Log in; search catalogue for "Uygulamalı Girişimcilik Eğitimi" (8 saat / 4 modül).
    4. Enroll; accept online async format if available (faster than waiting for a sync cohort).
    5. Capture confirmation email.
  • Deliverable: Confirmation email in inbox; screenshot saved to outputs/kosgeb/enrollment_confirmation.png.
  • Gotchas:
    • Tarayıcı uyarısı: KOSGEB portal works best on Chrome / Edge. Safari sometimes fails on the e-Devlet redirect. Firefox is iffy.
    • If the portal requires an "aktif girişimci adayı" flag, it means they are routing you to the girişimci (not already-founded) version — you want the "girişimci" track even if you already have Ltd.Şti.; this course is a prerequisite that the program still accepts post-founding.
    • Some cohorts have live Zoom sessions at fixed hours — if your schedule cannot accommodate, pick async.

T05 — Draft NACE change petition (conditional)

  • What: Write a 1-page Turkish petition to "Ticaret Sicil Müdürlüğü" requesting NACE code update from current to target (62.01.01 or 63.12.01).
  • Why: If current NACE already matches target, skip entirely (mark T05–T06 N/A and reclaim 60 min). Otherwise, this petition is the legal instrument that triggers the NACE update. Without it, you cannot file KBS (T13–T15) with the right sector code and KOSGEB will classify you incorrectly.
  • How:
    1. Use TOBB template (search "TOBB NACE değişiklik dilekçe örneği").
    2. Address: "[İl] Ticaret Sicil Müdürlüğü'ne". Include: unvan, ticaret sicil no, eski NACE, yeni NACE, gerekçe (1 paragraf: "teknoloji odaklı faaliyetler, yazılım geliştirme ağırlığı..."), imza.
    3. Save as outputs/legal/nace_change_petition_draft.docx.
  • Deliverable: DOCX file, addressed to Sicil Müdürlüğü.
  • Gotchas:
    • Ltd.Şti. için imza yetkisi olan ortak imzalar; A.Ş. için yönetim kurulu kararı eklenmesi gerekebilir (kuruluş sözleşmesinde NACE yazılıysa ana sözleşme değişikliği şart → noter + genel kurul → 2–3 hafta uzar). Before drafting, check your ana sözleşme for explicit NACE reference. If present, you need a full ana sözleşme tadili, not a simple petition — in that case, consult your mali müşavir before submitting, and the 30-day plan may need to drop T05–T06 and leave NACE for Horizon-2.

T06 — Submit NACE change petition

  • What: File the petition via MERSİS online or in person at Ticaret Sicil Müdürlüğü.
  • Why: Without filing, the petition is just a draft — the sicil update triggers only upon submission. Expect 3–5 business day processing.
  • How:
    1. Log into mersis.gtb.gov.tr with e-Devlet.
    2. "Başvuru / Değişiklik" → "Faaliyet Konusu (NACE) Değişikliği."
    3. Upload petition PDF + gerekirse ana sözleşme tadil tasarısı.
    4. Submit; capture başvuru numarası.
    5. Log ref in outputs/legal/nace_change_tracking.md with date + başvuru no.
  • Deliverable: Başvuru numarası recorded.
  • Gotchas:
    • MERSİS sometimes redirects to a separate TOBB portal for in-person appointment if the change type requires physical submission. If that happens, book the earliest TOBB slot (often same-week).
    • Ana sözleşme tadili gerekiyorsa: MERSİS flow is different — you submit the tadil tasarısı for Sicil approval, then ilan in Türkiye Ticaret Sicil Gazetesi, then the NACE change becomes legally effective. This takes 2–3 weeks, not 3–5 days.

T20 — Book noter appointment for imza sirküleri

  • What: Book a noter slot to issue a fresh imza sirküleri.
  • Why: Investor data room (T56) and many grant submissions require imza sirküleri <6 ay old. Noters can have 1–2 week waitlists; booking on D2 ensures T21 happens within Week 2–3.
  • How:
    1. Open https://randevu.noterlik.org.tr (or call your usual noter).
    2. Pick nearest noter; select service "İmza Sirküleri."
    3. Book earliest slot; confirm.
    4. Log date in outputs/legal/noter_appointment.md.
  • Deliverable: Appointment confirmed.
  • Gotchas:
    • Some noters require you to bring the ana sözleşme + son ticaret sicil gazetesi + TC kimlik. Bring originals + 2 photocopies.
    • If NACE petition (T06) is in flight, imza sirküleri issued before the NACE change completes still works — imza sirküleri is about signatory authority, not faaliyet konusu. Don't wait for NACE.

T23 — Dispatch finance-fpa for KOSGEB model

  • What: Write the dispatch brief for finance-fpa agent to produce a 36-month P&L + cash flow.
  • Why: finance-fpa runs as a sub-agent; it needs an explicit brief with input contract. Without a written brief, the agent will produce generic output that does not fit KOSGEB's template. This task is the handoff, not the modelling itself.
  • How:
    1. Create journal/2026-04-23_founder_dispatch_finance-fpa_kosgeb-model.md.
    2. Brief structure (template):
      • Goal: 36-mo P&L + cash flow for KOSGEB İleri iş planı.
      • Inputs: current ARR (if any), headcount plan (1 founder today + 1 Ar-Ge hire M6 + 1 growth hire M9), cloud + SaaS costs, KOSGEB grant assumption (1.1M TL spread over months), marka tescil fee.
      • Output format: monthly Y1, quarterly Y2–Y3, xlsx at outputs/finance/kosgeb_36mo_model.xlsx + 1-page summary.
      • Deadline: D7 2026-04-28.
      • Escalation: slack/journal comment if any input missing.
  • Deliverable: Dispatch file exists with input contract.
  • Gotchas:
    • Don't bundle the investor model into the same brief — different template requirements; T26 is a separate dispatch.
    • Reference the most recent reconciled P&L (commit 199fe39 per plan §5) as starting baseline so the agent doesn't re-derive from zero.

T26 — Dispatch finance-fpa for investor model

  • What: Second dispatch brief for the investor-facing financial model.
  • Why: Parallel to T23, different audience. Investor model needs GMV / take-rate / CAC / LTV / payback / burn — KOSGEB model doesn't. Separate brief prevents the agent from confusing requirements.
  • How:
    1. Create journal/2026-04-23_founder_dispatch_finance-fpa_investor-model.md.
    2. Brief: 36-mo P&L (monthly Y1, quarterly Y2–Y3), explicit rows for GMV, take-rate %, CAC, LTV, payback months, burn. Output: outputs/finance/glossgo_investor_model.xlsx. Deadline D13.
  • Deliverable: Dispatch file exists.
  • Gotchas:
    • Investor model assumes the raise decision (T29) hasn't happened yet — use placeholder "$250K @ $2M post (Q5 default)" and flag for update once T29 completes.
    • Don't give the agent a pre-built excel to fill in — give it the metric list and let it structure. Over-specifying output shape produces brittle models.

T36 — Decide target Teknopark (partial)

  • What: Start the İTÜ ARI vs Teknopark İstanbul (vs Bilkent Cyberpark if Ankara-based) decision. 15 min today, finish D3.
  • Why: Teknopark choice gates the application pack (T37), checklist (T38), and proposal drafts (T39–T43). Wrong park = wrong template = rewrite. İTÜ ARI is strongest signal for consumer tech + Istanbul; Teknopark İstanbul is broader; Bilkent is Ankara only.
  • How:
    1. Pull 3 criteria: location (İstanbul → ARI or Teknopark İstanbul; Ankara → Bilkent), cohort calendar (check 2026 application windows), cost (ARI ~6K TL/ay virtual, TP İst ~4K TL/ay).
    2. Today: list the 2 candidates in entity-form-decision file with pros/cons. Decision deferred to D3.
  • Deliverable: Decision draft in file.
  • Gotchas:
    • İTÜ ARI has stricter kabul — they want Ar-Ge projesi with measurable yenilik unsuru. If your R&D angle is weak, TP İstanbul is easier to get into.
    • Office mode (Q10, T64) matters here: if you will physically move, ARI rent is higher; virtual, cost drops ~40%.

Day 3 — 2026-04-24 (Fri)

T36 — Finish Teknopark decision

  • What: Commit to İTÜ ARI or Teknopark İstanbul. Log rationale.
  • Why: Gating T37–T43 (Teknopark application pack + 5-section R&D proposal).
  • How:
    1. Revisit D2 pros/cons list.
    2. Default per roadmap Q10: İTÜ ARI, virtual office mode.
    3. Log decision line: "Teknopark: İTÜ ARI · mode: virtual · rent: ~6K TL/ay · başvuru window: [verify on park site]."
  • Deliverable: Decision in file.
  • Gotchas: Park websites occasionally publish separate "yazılım" vs "biyoteknoloji" tracks — confirm which track fits GlossGo (yazılım).

T37 — Download Teknopark application pack

  • What: Download the chosen park's başvuru paketi PDF.
  • Why: The pack defines required sections — without reading it, you cannot draft the proposal correctly. Every park has a slightly different template.
  • How:
    1. Navigate to park site (e.g. ariteknokent.com.tr for İTÜ ARI).
    2. "Başvuru" / "Firma Kabul" menu → download the current başvuru formu + değerlendirme kriterleri PDFs.
    3. Save to outputs/teknopark/ariteknokent_basvuru_paket.pdf.
  • Deliverable: PDF saved.
  • Gotchas:
    • Parks update templates annually (usually Ocak–Şubat). Ensure you downloaded the 2026 version, not 2025.

T44 — Assemble founder + planned hire CV PDFs

  • What: Combine founder CV + drafted Ar-Ge engineer spec into one PDF.
  • Why: Teknopark panel evaluates ekip kapasitesi. The Ar-Ge engineer doesn't need to be hired yet — a written rol tanımı + gerekli beceriler suffices — but the founder CV must be polished.
  • How:
    1. Export your LinkedIn PDF or existing CV; update to 2026.
    2. Write a 1-page Ar-Ge engineer rol tanımı (iş tanımı, aranan beceriler, maaş bant, başlama tarihi).
    3. Merge: outputs/teknopark/cvs.pdf.
  • Deliverable: Single PDF, 2+ pages.
  • Gotchas:
    • If you have no tech co-founder (Q4 open), explicitly flag in the Ar-Ge engineer section: "Technical co-founder yet-to-be-recruited; Ar-Ge engineer is first hire post-grant." Teknopark panels accept this if the founder has technical depth; otherwise they score low.

T45 — Start marka tescili on turkpatent.gov.tr

  • What: Register an account, start "GlossGo" marka başvurusu draft.
  • Why: KOSGEB İGDP (İşletme Geliştirme Destek Programı) refunds marka tescil ücretini up to 30K TL — so marka başvurusu pays for itself if the business is KOSGEB-registered (which happens via T15 KBS). Also protects brand before investor outreach.
  • How:
    1. https://www.turkpatent.gov.tr → register with TC kimlik.
    2. "Marka Başvurusu" → draft new application.
    3. Fill unvan, marka adı "GlossGo", 42. sınıf (teknoloji hizmetleri), 35. sınıf (reklam / pazarlama), 44. sınıf (güzellik hizmetleri).
    4. Save draft; do not submit yet (T47).
  • Deliverable: Draft saved on portal, ref no. visible.
  • Gotchas:
    • Sınıf seçimi para maliyeti belirler: her sınıf ~2.5K TL. Start with the 3 most-important classes; expand later if needed.
    • Check marka önceliği: same-name registrations in the chosen classes kill your application. Use portal's "Marka Araştırma" first — if a blocking registration exists, consult a marka vekili before submitting.

T46 — Pay marka tescil fee

  • What: Pay the başvuru ücretini online.
  • Why: Required before submission.
  • How:
    1. From draft application page, "Ödeme Yap".
    2. Credit card or EFT. Download receipt.
    3. Save to outputs/legal/marka_tescil_odeme.pdf.
  • Deliverable: Receipt saved.
  • Gotchas:
    • EFT takes 1 biz day; kredi kartı anında. Use card unless cost is above credit-card limit.

T47 — Submit marka başvurusu

  • What: Finalize and submit the application; capture başvuru numarası.
  • Why: Submission anchors a marka öncelik tarihi — the earlier, the stronger the claim against any later conflicting registration.
  • How:
    1. Portal → draft → "Başvuruyu Tamamla ve Gönder".
    2. Confirm; capture başvuru numarası (format: 2026/XXXXXX).
    3. Log in outputs/legal/marka_basvuru.md.
  • Deliverable: Başvuru no. logged.
  • Gotchas:
    • Reference date = submission date — do not delay between pay (T46) and submit (T47).
    • Marka tescili itself takes 6–8 ay; for 30-day plan, only the başvuru numarası matters.

Day 4 — 2026-04-25 (Sat) — weekend, reserved

No scheduled tasks. Rationale: founder capacity is 10h/week weekdays only per §3 of plan. Saturdays are buffer only if a weekday task slips — do not preload.

Day 5 — 2026-04-26 (Sun) — weekend, reserved

Same as D4. Use this time to review Week 1 outputs, update the status tracker, and prep mentally for Week 2 KOSGEB modules.

§3 Week 2 — summary treatment (Days 6–10)

D6 Mon 04-27. T08 (confirm education slot, 10 min): log the exact date the first module becomes available on kosgebakademi.gov.tr. T38 (read Teknopark app pack, build checklist, 45 min): scan the downloaded PDF, extract required sections + eklenecek belgeler into a 1-page markdown checklist. T39 (R&D proposal §1 proje tanımı, 45 min): name, amaç, kapsam — use roadmap §3.2 Teknopark framing as seed. T21 (noter visit for imza sirküleri, 45 min if slot hits today): bring unvan, TC, ana sözleşme; receive original + 2 suretler; save scan. Gotcha: noter may require e-imza holder present to be a yetkili ortak — check noter requirements before you arrive.

D7 Tue 04-28. T09 (Girişimcilik Eğitimi module 1, 60 min): log into portal, complete modül 1 + any quiz. T40 (R&D proposal §2 yenilik + teknik zorluklar, 60 min): the most important section — panel evaluators anchor on this. Frame GlossGo's Ar-Ge as "çok taraflı eşleştirme algoritması + dinamik fiyatlandırma" or similar. T13 (open KBS form, 15 min): only if NACE petition returned with updated code; otherwise defer to D8–D9. Portal: edevlet.kosgeb.gov.tr → login with e-Devlet → KBS Beyannamesi. Gotcha: KBS form session times out after 20 min of inactivity — save draft frequently.

D8 Wed 04-29. T10 (module 2, 60 min), T41 (R&D proposal §3 takvim, 30 min — 12–36 ay milestones), T14 (fill KBS draft, 30 min — headcount, 2025 revenue, sector fields). KBS 2025 revenue field: use gerçekleşen ciro; if <3M TL, you are mikro KOBİ which is what KOSGEB İleri wants. Gotcha: the KBS ciro field wants figures in TL, not thousands — off-by-1000 error is easy and downgrades you to a wrong KOBİ tier.

D9 Thu 04-30. T11 (module 3, 60 min), T15 (submit KBS beyannamesi, 15 min — download confirmation PDF), T25 (review finance-fpa KOSGEB model, 30 min — verify row totals, check Y1 sum against expected ARR, approve or list changes in dispatch file), T48 (dispatch investor-relations for teaser, 15 min — brief should include entity form, raise size from T29 if done, or flag as TBD), T18 (request Faaliyet Belgesi from TOBB, 15 min — online at tobb.org.tr chamber portal with e-Devlet, 2K TL fee, 1–2 biz day issuance). Gotcha: İstanbul chamber has both online and in-person counters; online is faster but requires e-imza. If no e-imza, physical counter at Sütlüce is 30 min round trip.

D10 Fri 05-01. Labour Day. No work. Reschedule Friday review to Mon 05-04.

D11–D12 weekend. Reserved.

§4 Week 3 — summary treatment (Days 11–15)

D13 Mon 05-04. T12 (module 4 + final quiz, 60 min → certificate download; save to outputs/kosgeb/girisimcilik_egitimi_sertifika.pdf). T42 (R&D proposal §4 bütçe, 45 min — personel + altyapı kalemleri; bind to finance-fpa Y1 numbers). T19 (pick up Faaliyet Belgesi, 15 min — online download or chamber counter). Friday-review-rescheduled (30 min, not counted as task). Gotcha: if quiz fails, portal allows retry but may schedule after cooldown — do the quiz carefully. The certificate PDF has an unique doğrulama kodu; the PDF alone is sufficient for KOSGEB submission.

D14 Tue 05-05. T43 (proposal §5 çıktı + etki, 30 min — impact metrics: GMV reach, istihdam yaratımı, Ar-Ge kazanımı). T27 (review investor model output, 30 min — should have been delivered by now; if not, journal-chase finance-fpa). T28 (approve or list changes, 30 min). T29 (decide raise size + valuation, 15 min — default $250K @ $2M post). T30 (equity appetite decision, 15 min — "raise H2 2026" OR "grants-only through Oct"). Gotcha: T29 and T30 feel like strategic 2-hour decisions but should be 15 min each — you are committing to defaults. Real valuation gets set by market (first term sheet); what matters now is the anchor you put in the teaser.

D15 Wed 05-06. T31 (iş planı §1 mission/market/problem, 45 min), T32 (§2 personel planı, 45 min). Template source: KOSGEB İleri official iş planı word; headings are standardized. T49 (investor-relations delivers teaser v1 → T50 founder review, 15 min — check tone, numbers, ask amount). T54 (dispatch investor-relations for data room, 15 min — 6 categories). Gotcha: iş planı §1 should be under 2 pages — panel evaluators skim. Front-load the hook (GlossGo: Turkish beauty-tech marketplace, $X TAM, Y traction).

D16 Thu 05-07. T33 (iş planı §3 opex, 45 min — cloud AWS/Cloudflare, SaaS, marka tescil, consulting). T51 (dispatch investor-relations for deck v1, 15 min). T57 (dispatch for long-list, 15 min). T34 (paste finance tables into §4 finansal projeksiyon, 30 min — copy from approved kosgeb_36mo_model.xlsx). Gotcha: don't re-type finance numbers into the iş planı — paste as linked table or embedded image; manual re-keying introduces errors and KOSGEB panels spot cross-sheet inconsistencies.

D17 Fri 05-08. T35 (§5 takvim + bütçe + use of funds, 45 min — explicit KOSGEB grant ask + match funding table). T55 (data room index delivered) + T56 partial (upload ticaret sicil gazetesi, vergi levhası, imza sirküleri to data_room/legal/, 15 min). T64 (Teknopark office mode decision line, 15 min — virtual, ~6K TL/ay). Friday review. Gotcha: data room "Legal" folder should not contain SGK borcu yok or vergi borcu yok letters — those are private compliance artifacts, not investor due-diligence; keep them in outputs/legal/ only.

§5 Week 4 — summary treatment (Days 16–22)

D20 Mon 05-11. T52 delivered → T53 founder deck review (45 min — 15 slides against checklist: problem clarity, traction numbers, ask, team slide; list changes). T56 finalize legal uploads if still pending (15 min). T21 noter visit buffer slot (45 min if still outstanding — must complete before W4 close). T58 long-list delivered; confirm receipt (5 min). Gotcha: deck review — do not polish slide design today; review content only. Design polish is a separate pass and often not needed for warm-intro outreach.

D21 Tue 05-12. T59 (review long-list, mark top-10 priorities with preferred intro paths, 45 min). T60 (draft Galata Business Angels intro ask, 30 min — <150 words, LinkedIn format: who you are, why GlossGo, specific ask = warm intro to BAN manager). T61 (draft Arya Women Investment intro, 30 min — emphasize founder diversity angle if applicable). Gotcha: LinkedIn DM character limits (~300 chars for connection request note) — draft for both DM and email, use email body for longer pitch.

D22 Wed 05-13. T62 (draft Keiretsu Forum Turkey intro, 30 min). T63 (send all 3 warm-intro messages on LinkedIn, 15 min — screenshot each sent message; save to outputs/investor/intros_sent/). Buffer (60 min) for iş planı or proposal polish spillover. Gotcha: send messages before 17:00 İstanbul time — angel managers read inbox end-of-day; morning delivery + weekday = higher reply rate than Friday evening.

D23 Thu 05-14. Iş planı polish for submission-readiness (60 min — proofread, verify cross-references, embed PDFs if template allows). Teknopark proposal polish (45 min — same pass). Status tracker update (15 min). Gotcha: polish pass should catch Turkish dilbilgisi hataları — run through a Turkish proofreader (a colleague or paid Yeminli Tercüman) before submission; panel evaluators downgrade on obvious typos.

D24 Fri 05-15. Buffer day (120 min) for any overdue task. Friday review. Gotcha: if by D24 you still have 3+ overdue tasks, triage: Legal/KOSGEB > Teknopark > Investor. Cut investor (deck can slip to next cycle); never cut Legal.

D25–D26 weekend. Reserved.

D27–D29 2026-05-18 to 05-20. Plan tail: review warm-intro replies (draft follow-up schedule), draft T68 30-day handoff note (5 bullets: what's done, what's blocked, what's deferred, what next cycle should pick up, key learnings), final status-tracker review, close cycle. Gotcha: the handoff note is the input for next cycle's task-decomposer — thin handoffs produce bad next plans. Spend the full 30 min.

§6 Agent handoffs explained

Eight agent-dispatched or agent-involving tasks. All pre-authorized per plan §5 except H7 and H8 which await founder green light.

H1 — finance-fpa KOSGEB 36-month P&L (T23 dispatch → T24 delivery)

  • Agent: finance-fpa.
  • Founder brief path: journal/2026-04-23_founder_dispatch_finance-fpa_kosgeb-model.md. Template structure: Goal / Inputs (headcount, cloud costs, grant assumption, baseline P&L reference) / Output contract (xlsx path, sheet structure) / Deadline / Escalation.
  • Agent returns: outputs/finance/kosgeb_36mo_model.xlsx + journal/2026-04-28_finance-fpa_kosgeb-model.md summary.
  • Founder review: open xlsx, check row-sum consistency, Y1 ARR vs expected, grant spread matches KOSGEB disbursement schedule. Approve by writing Status: APPROVED line in dispatch file, or list changes.
  • Founder action with output: paste Y1 monthly P&L + cash flow into iş planı §4 (T34).

H2 — finance-fpa investor model (T26 → T27)

  • Agent: finance-fpa.
  • Brief: journal/2026-04-23_founder_dispatch_finance-fpa_investor-model.md. Same template, inputs differ: must include GMV growth curve assumption, take-rate trajectory, CAC inputs.
  • Returns: outputs/finance/glossgo_investor_model.xlsx with 6 unit-economics rows.
  • Review: check LTV/CAC ≥ 3, payback < 18 mo, burn matches implied runway given raise size.
  • Action: numbers feed teaser (T49) + deck v1 (T52) via investor-relations agent.

H3 — investor-relations 1-page teaser (T48 → T49)

  • Agent: investor-relations.
  • Brief: journal/2026-04-30_founder_dispatch_investor-relations_teaser.md. Inputs: approved investor model, raise + valuation (T29/T30), roadmap §7 framing.
  • Returns: outputs/investor/teaser_v1.pdf, 1 page.
  • Review (T50): checklist — problem clear in 2 lines, traction specific (avoid "significant growth" — use numbers), ask explicit ($X for Y months runway). Decision line in dispatch file.
  • Action: input to deck (T51) and to warm-intro attachments (T63 optionally).

H4 — investor-relations 15-slide deck v1 (T51 → T52)

  • Agent: investor-relations.
  • Brief: separate dispatch file. Inputs: approved teaser, approved investor model, entity decision, cap table stub. 15 slots per roadmap §6.3.
  • Returns: outputs/investor/deck_v1.pdf, 15 slides.
  • Review (T53): content review first (numbers, ask, team), design second (not in scope for v1). Decision line.
  • Action: used in BAN panel pitches (Horizon-2), not yet in D22 warm-intros (those use teaser only).

H5 — investor-relations data room index (T54 → T55)

  • Agent: investor-relations.
  • Brief: journal/2026-05-06_founder_dispatch_investor-relations_data-room.md. Inputs: 6 categories (legal, cap_table, IP, metrics, contracts, misc), raise decision.
  • Returns: outputs/investor/data_room_INDEX.md + 6 empty folders.
  • Review: index readable, folder names match expected.
  • Action: founder fills folders (T56) — this is the mechanical part, not the agent's job.

H6 — investor-relations 23-name long-list (T57 → T58)

  • Agent: investor-relations.
  • Brief: journal/2026-05-07_founder_dispatch_investor-relations_longlist.md. Inputs: roadmap §3.8, §3.9, §7.5 target lists; stage pre-seed; ticket $100K–$500K.
  • Returns: outputs/investor/longlist_v1.md with 23+ rows × 5 warm-intro paths each.
  • Review (T59): founder marks top-10 priority + preferred intro path per priority target.
  • Action: drives T60–T63 (warm-intro asks for top 3 BANs first).

H7 — turkey-funding-research verify cap/BKY figures (proposed)

  • Agent: turkey-funding-research (same agent that wrote the roadmap).
  • Awaiting founder approval. Not critical path. Dispatch only if founder wants fresh figures before Horizon-2 submission.
  • Brief if approved: single question — "verify 2026 KOSGEB İleri cap (1.1M TL grant + 300K TL loan) and BKY 75/100 split against current sources as of 2026-05-05."
  • Returns: 1-line journal update with URL + date.
  • If skipped: use roadmap as-of figures and flag "verify before submission" in next cycle.

H8 — next-cycle task-decomposer (proposed, horizon end)

  • Agent: task-decomposer.
  • Founder green-lights via T68 handoff note completion.
  • Brief: handoff note + completion tracker + any new founder decisions from Weeks 1–4.
  • Returns: Horizon-2 (days 31–60) plan: KOSGEB İleri actual submission, Teknopark panel pitch, BKY lisans application, angel-round outreach response handling.
  • Action: founder starts Horizon-2 from 2026-05-22.

§7 The 10 open questions — decision guide

Q1 — A.Ş. or Ltd.Şti.?

  • Why matters: gates T01, T05, T31–T35, cap-table work in T56. Investor-facing narrative differs.
  • Good default: keep Ltd.Şti. through 2026 grants, convert to A.Ş. before first priced angel term sheet.
  • Reversibility: reversible but expensive (~25K TL + 3 weeks for nev'i değişikliği).
  • Time to decide: 5 min (pick default, move on).

Q2 — Current NACE code?

  • Why matters: gates T03, T04, T05, T06, T13–T15, T18, T23, T24, T31. If code is wrong, every KOSGEB/Teknopark form misclassifies.
  • Good default: if current NACE is already 62.xx or 63.12.01, skip T05–T06. Otherwise file petition to 62.01.01.
  • Reversibility: NACE changes are reversible but cost 3–5 biz days per change.
  • Time to decide: 5 min (look at TSG PDF, compare to 62.01.01).

Q3 — Payroll + Ar-Ge personnel count?

  • Why matters: finance-fpa P&L (T24), iş planı personel planı (T32), Teknopark proposal (T40, T42).
  • Good default: 1 founder today + 1 Ar-Ge engineer (hire M6) + 1 growth hire (M9) — matches KOSGEB İleri grant absorption capacity.
  • Reversibility: fully reversible (plan numbers, not actual hires).
  • Time to decide: 30 min (requires thinking about burn vs runway).

Q4 — Technical co-founder with lisans+?

  • Why matters: BİGG eligibility (deferred to Horizon-2), Teknopark panel scoring, proposal strength.
  • Good default: if no tech co-founder, defer BİGG to next cycle and keep Teknopark proposal modest (1 Ar-Ge hire, not a full team).
  • Reversibility: reversible — you can recruit a tech co-founder later and refile.
  • Time to decide: 30 min (honest self-assessment of founding team).

Q5 — Equity appetite 2026?

  • Why matters: T29, T30, all investor outreach (T48, T51, T54, T57, T60–T63).
  • Good default: raise $250K pre-seed angel in H2 2026; use BKY tax lever.
  • Reversibility: reversible until you sign first term sheet.
  • Time to decide: 30 min (one focused conversation with self or co-founder).

Q6 — Co-founder bonus status (kadın/genç/gazi)?

  • Why matters: T22, T31, T32 (KOSGEB grant uplift).
  • Good default: claim only what is documentable.
  • Reversibility: cannot claim retroactively on a submitted form without re-submission.
  • Time to decide: 5 min (self-evident).

Q7 — İstanbul-based?

  • Why matters: T36 (Teknopark choice), İSTKA eligibility (Horizon-2).
  • Good default: Yes (routes Teknopark to İTÜ ARI).
  • Reversibility: irreversible short-term (cannot relocate company in 30 days).
  • Time to decide: 1 min (binary fact).

Q8 — Existing SHA / ortaklık yapısı?

  • Why matters: T56 cap-table section, T28 (investor model assumes current ownership).
  • Good default: founder 100% until angel round triggers cap-table reset.
  • Reversibility: actual SHA changes require sicil değişikliği.
  • Time to decide: 5 min (read existing ana sözleşme).

Q9 — Target pre-seed valuation?

  • Why matters: T29, T59, T60–T62 (anchor in warm-intro messages).
  • Good default: $2M post-money for $250K raise (12.5% dilution).
  • Reversibility: anchor only; market sets actual valuation.
  • Time to decide: 15 min (spot-check against 3 recent TR consumer-marketplace seeds).

Q10 — Office relocation to Teknopark?

  • Why matters: T36, T64, monthly OpEx in finance model.
  • Good default: virtual office mode at İTÜ ARI (low cost, meets zone requirement for vergi istisnası).
  • Reversibility: fully reversible (switch virtual to physical anytime).
  • Time to decide: 15 min.

Total decision budget for all 10 questions: ~2.5 hours. Complete all 10 by end of Day 1 morning so Week 1 is unblocked.

§8 Weekly ritual — Friday review

What you review (30 min, every Friday):

  1. Open journal/2026-04-21_founder_funding-status-tracker.md.
  2. Scan this week's expected completions (from plan §3 Week checkpoint).
  3. For each row: mark done / doing / blocked / deferred. Add a blocker note if blocked.
  4. Look at next week's batch in plan §3. Confirm you can hit capacity (120 min/day weekday).
  5. If >3 tasks are blocked, write a 2-line note in the tracker: "Week risk: . Mitigation: ."

Marking tasks done:

  • Status column: done only when the done-check in plan §1 is verifiably true (file exists at path, line contains required content, etc.).
  • Never mark done if the deliverable is "mostly written" — that's doing.

When to trigger task-decomposer cycle 2:

  • Recommended: Sun 2026-05-18 evening, after D27 buffer day.
  • Dispatch via H8: write T68 handoff note, then create a new dispatch brief journal/2026-05-18_founder_dispatch_task-decomposer_cycle-2.md pointing to the handoff + tracker + any new decisions.
  • Cycle-2 scope: Horizon-2 days 31–60 → KOSGEB İleri actual submission, Teknopark panel pitch prep, BKY lisans application, angel-round warm-intro reply handling.

§9 When things go wrong

NACE change rejected by Ticaret Sicil

  • Likely cause: ana sözleşme explicitly lists current NACE → requires ana sözleşme tadili (noter + genel kurul kararı).
  • Recovery: consult mali müşavir immediately. Drop T05–T06 from the 30-day plan; fold NACE change into Horizon-2 as a 3-week sub-flow. Continue with current NACE on KBS (T14) but flag in iş planı §1 that NACE petition is in-flight.
  • Impact: T13–T15 KBS accuracy degraded; KOSGEB submission (Horizon-2) may need re-file after NACE finalized.

KOSGEB Girişimcilik Eğitimi slot unavailable this week

  • Likely cause: high demand, next sync cohort 2–3 weeks out.
  • Recovery: switch to async format if available; if fully booked, enroll in alternative accredited provider (İŞKUR, TOBB Akademi also offer KOSGEB-recognized equivalents). Verify acceptance with KOSGEB İl Müdürlüğü before enrolling in a non-kosgebakademi course.
  • Impact: if education slips past D13, T12 certificate arrives after horizon; KOSGEB submission (Horizon-2) delays by education gap.

SGK or vergi borcu var (unexpected debt)

  • Recovery: call 170 (SGK) or your vergi dairesi to get debt breakdown. Pay via İVD or Halkbank same day. Re-request borcu yok letter 24–48h later.
  • Impact: 1–2 day slip on T16/T17; no downstream impact if caught in Week 1.
  • Prevention: run both checks on D1 even if you "know" there is no debt — late-paid KDV or gecikme faizi can surprise you.

Ticaret Sicil Gazetesi not found online

  • Likely cause: very old ilan, pre-digital archive, or unvan change causing search miss.
  • Recovery: request "Ticaret Sicil Gazetesi örneği" from TOBB chamber — same form as Faaliyet Belgesi (T18), ~2-3 biz days, ~200 TL fee. Physical copy issued; scan to PDF.
  • Impact: 2–3 day slip on T02 → T03 → T04 chain. Mitigate by parallelizing: request physical copy on D1 morning, work other D1 tasks in afternoon.

Founder has not answered 1+ open question by end of Week 1

  • Recovery: apply the suggested defaults from §7 above. Log the default as the decision with note "default applied — revisit by D15 if new info." Continue.
  • Impact: silent progress; decisions remain reversible; prevents cascade delay.
  • Escalation trigger: if 4+ questions still open at D15, pause the plan and run a focused 2-hour decision session before continuing Week 3.

finance-fpa agent misses deadline on T24 or T27

  • Recovery: journal-chase via comment on dispatch file. If no response in 24h, fall back to founder self-extending existing cycle-2 reconciled P&L (commit 199fe39) to 36 months manually (~60 min).
  • Impact: T25/T28 approval slips 1 day; iş planı §4 population (T34) slips accordingly.

investor-relations deck v1 not usable

  • Recovery: self-author using the 15-slot skeleton from roadmap §6.3. Do not polish beyond content.
  • Impact: D22 warm-intros still go out using teaser (T49) only; deck moves to Horizon-2.

§10 Budget of time, money, and agent dispatches

Week Founder time (min scheduled) Cash out of pocket (TL) Agent dispatches
W1 (D1–D5) 370 min ~5,000–10,000 TL (marka tescil fee + sınıf başı ~2.5K × 3 sınıf = 7.5K; borcu yok letters = 0 TL; noter imza sirküleri booking = 0 TL today) 2 (finance-fpa KOSGEB model, finance-fpa investor model)
W2 (D6–D10) 490 min ~1,500 TL (noter imza sirküleri ~1K–1.5K TL on D6; Faaliyet Belgesi request on D9 ~200 TL) 0 (agents working in background)
W3 (D13–D17) 555 min ~500 TL (misc: eğitim sertifikası ücretsiz, Faaliyet Belgesi pickup 0 TL extra) 4 (investor-relations teaser, data-room, deck, long-list)
W4 (D20–D24) 575 min 0 TL (polish + outreach, no new fees) 0 (receiving outputs)
W5 partial (D27–D29) 345 min 0 TL 0 (handoff prep)
Total 30 days ~2,335 min (38.9 h) + ~180 min buffer = 2,515 min (~42 h) ~7,000–12,000 TL 6 agent dispatches (+2 proposed: H7, H8)

Capacity margin: 22 working days × 120 min = 2,640 min. Plan uses ~2,515 min → 4–5% headroom. Tight.

Cash notes:

  • Figures exclude unforeseen SGK / vergi debt clearance (should be 0 if healthy).
  • NACE change petition itself is free; ana sözleşme tadili (if needed) adds ~3,000–5,000 TL noter + ilan.
  • If you skip marka tescili 2 of 3 sınıf, reclaim ~5,000 TL.

Agent dispatch notes:

  • 6 pre-authorized: 2 finance-fpa + 4 investor-relations.
  • 2 proposed (require founder green-light): H7 turkey-funding-research verify, H8 next-cycle task-decomposer.

End of companion document.