Improvements & ideas log¶
A running list of ideas, feedback, and process improvements — so they don't get lost in chat or wait for a meeting to surface. Drop anything here the moment you think of it; triage later.
This is the home for half-formed ideas, friction you hit, "we should…" thoughts, and feedback on how the team works. Capturing beats remembering. If it's worth a Slack message, it's worth a row here.
How to add an entry¶
Add a row to the log — one line, link out if it needs detail. Three ways; pick whatever's fastest:
- From this page (no setup): click the ✏️ Edit pencil at the top right → it opens this file in the GitHub editor → add a row → Commit changes. (Needs access to the private
scailetech/playbookrepo.) - In Claude Code: open the repo and say "log this idea: …" — it appends a properly-formatted row and commits for you.
- Direct in git: edit
docs/13-ideas/ideas-and-feedback.md, commit, push.
Column values:
- Type —
idea·feedback·improvement·question - Status —
new·exploring·in progress·blocked·done·parked - Owner — who carries it, or
unassigned
No gatekeeping — drop it in as new and it gets triaged later. Capturing beats remembering.
Log¶
| Date | Item | Type | Status | Owner |
|---|---|---|---|---|
| 2026-06-12 | Expand this playbook beyond FAs to all roles (engineering, GTM, product, ops) | improvement | in progress | current FA |
| 2026-06-12 | Host the playbook on GitHub under the scailetech org so the whole team can access it |
improvement | done — scailetech/playbook | current FA |
| 2026-06-12 | Connect Vercel to the GitHub repo for auto-deploy on push | improvement | done — live on the scailetech Vercel team; auto-deploys on every push to main |
current FA |
| 2026-06-12 | Make the playbook queryable in Claude Code so new hires self-serve instead of asking the team | idea | done (clone + Claude Code via CLAUDE.md; MCP optional) |
current FA |
| 2026-06-12 | Resolve Julius Petzla — corrected to Julius Betzler, CTO (per scaile-knowledge-base) |
question | done | Abir |
| 2026-06-12 | Decide whether team titles mirror the public about-us (Niccolo's public title is FA; Anton is a co-founder) or keep the brief's operating framing | question | new | Simon / Niccolo |
| 2026-06-12 | Define the Day 60 and Day 90 FA benchmarks | feedback | new | Simon |
| 2026-06-12 | Document the GTM system well enough that an FA can run it | improvement | done — active-gtm-system.md (sourced from the knowledge base; confirm with Niccolò) | Abir |
| 2026-06-12 | Optimize team headshot file sizes (Anton's is ~1.8 MB) for faster page loads | improvement | new | current FA |
| 2026-06-12 | Apply the "Precision Tech" design to the FA journey too, so both roadmaps match | idea | parked | current FA |
| 2026-06-14 | Onboarding gap (Kigentic): briefs are codenames/pitches, not specs — read critically, restate the task, pick a real venture name and confirm before building | feedback | done — onboarding guide §4 | Abir |
| 2026-06-14 | Onboarding gap (Kigentic): all infra (GitHub, Vercel, Supabase) must be under scailetech — request access day 1; added step-by-step project creation |
feedback | done — vercel-render-supabase.md | Abir |
| 2026-06-14 | Onboarding gap (Kigentic): confirm target-market language during briefing; flag a language gap day 0, not day 3 — it's a blocker | feedback | done — onboarding guide §5 | Abir |
| 2026-06-14 | New consolidated FA onboarding guide + Day 0 checklist + real Claude Code install/run steps (native installer, not npm) | improvement | done — onboarding guide | Abir |
| 2026-06-14 | Lock naming conventions (venture name vs codename, repo/project/domain slugs) — currently proposed defaults in the onboarding guide | question | new | August |
| 2026-06-14 | Which Claude plan does the FA use (Team?) and who adds you to the company account? | question | new | Simon / Niccolo |
| 2026-07-02 | Playbook clarity pass: removed the misleading "issue #N in the GitHub repo" wording and the phantom # column from Open-questions tables (no real GitHub issues exist), and cleaned placeholder/stub pages into clear "not-yet-written — owner X" states |
improvement | done | Abir |
| 2026-07-02 | Profile Sebastian — identified in the knowledge base as the person who sourced the Nextgentic (Kigentic) venture; full identity kept off this public page. Add to the roster if he's staff. | question | exploring | Simon / Niccolo |
| 2026-07-02 | "Jan-Dien" is not in the knowledge base — the second Intern FA there is Chandine (corrected on the team page). Confirm whether "Jan-Dien" is a real recent hire not yet in the KB. | question | exploring | Niccolo |
| 2026-07-02 | Decide whether the FA benchmarks (Day 60/90) and other open questions should become real GitHub issues, or stay as per-page playbook questions | question | new | Simon |
| 2026-07-02 | Fact-checked the playbook against scaile-knowledge-base: corrected team names/titles (Julius Betzler; Niccolò Casamatta = Head of GTM; Chandine as the 2nd FA), confirmed Kigentic → Nextgentic, and populated current-ventures / current-clients / active-gtm-system from the org repos (public-safe subset) |
improvement | done | Abir |
| 2026-07-02 | Playbook is publicly hosted — client pipeline, ARR, cap-table identities, and the insurance layer roadmap were deliberately kept OFF the living-layer pages. Decide whether to lock the site to team-only (Vercel auth) and add the full internal detail | question | new | Abir / Simon |
Owner: Current FA Last reviewed: 2026-06-12