Teemly Proof Room
Teemly · Workforce intelligence platform

Every claim, one click from the document behind it

The specifications, architecture, compliance roadmap and the full 214-task execution plan behind Teemly. Open any document, or click into any task to see why it exists, who owns it and how it gets done.

Browse 20 documentsExplore the 214 tasksOpen the data room folder ↗
20documents, all open 214tasks across 8 pillars 8trust and compliance tracks Jan 2027Phase 1 go-live target

Every document opens with one click, no sign-in or access request needed. Questions: info@teemly.co

Document library

20 documents, grouped by area

Every card opens the file directly, no sign-in needed. Versions and dates are shown on each card. All files also sit in one shared data room folder ↗.

Execution plan

One operating model, five waves to go-live and beyond

Every task maps to one of the eight pillars of the 8-Pillar Foundation and is ordered by dependency: nothing starts before what it depends on. Click a pillar or a wave to see its tasks.

Waves

NovDecJanFebMarAprMayJun
Today · 2 Nov

Tasks by pillar

88mandatory
25under way
0complete

Status from the live tracker, 2 Nov 2026.

Task explorer

All 214 tasks

Filter by wave, pillar, priority, owner or status. Click any task to open its instructions, definition of done and dependencies; task IDs inside a task jump to that task.

Showing 214 of 214 tasks

T-001Company OKRs & quarterly goalsFounder's Office & Strategy InputW0Mandatory DeepanNot started15-Nov-26

Why now. Every later task is ordered against a target. Without three to five written outcomes for Dec 2026 delivery and Jan 2027 launch, priorities drift and the team optimises locally.

Instructions

  1. Draft an OKR tree with one company objective per pillar that matters this quarter (Input, Transformation, Transmission, Conversion), each with 2-3 measurable key results.
  2. Deepan Cut to the 3-5 key results that decide success; name one owner per key result.
  3. Publish as a Doc and link each key result to the task IDs in this playbook.
  4. Team Review in the first weekly update of every month.

Done when

Signed-off OKRs with owners, published and linked to task IDs.

Inputs needed

Founder's view of the 12-month goal; TD funding milestones; current pipeline of 10 prospects.

Depends on

None. Can start now.

Unlocks

T-003 T-004 T-015 T-022 T-045 T-100 T-169

T-002Decision memosFounder's Office & Strategy InputW0Mandatory DeepanIn progress07-Nov-26

Why now. Two open decisions are the binding constraint on the whole build: the backend/agent stack (.NET native vs Python hybrid) and the delivery model (current vendor, another vendor, or in-house). Nothing in Engineering can be sequenced until both are decided.

Instructions

  1. Write one memo per decision: options, criteria (time to Dec delivery, Microsoft Store/signing fit, hiring market in Salem/Chennai, long-term cost, migration risk), scoring and a recommendation.
  2. Deepan Add context from vendor conversations; set a decision date no later than 7 Nov.
  3. Fold in evidence from the stack spike (T-006) and update the recommendation.
  4. Deepan Decide and record the decision at the top of the memo.

Done when

Both decisions recorded with date, rationale and owner.

Inputs needed

Lenin's note on Python delivery benefits; vendor quotes; candidate pipeline for the C#/.NET hire.

Depends on

None. Can start now.

Unlocks

T-006 T-021 T-024

T-003Business plan & scenariosFounder's Office & Strategy InputW0Mandatory DeepanIn progress15-Nov-26

Why now. The ₹1.5 Cr from TD must last 12 months. A plan with base, upside and downside cases shows how many months of runway each scenario buys and which hires or vendor spends can flex.

Instructions

  1. Build a 12-month plan (Excel) with headcount, vendor, infrastructure and GTM costs, linked to milestones.
  2. Add three scenarios with different launch dates and conversion rates; label all estimates.
  3. Deepan Lock assumptions with Sathya.

Done when

Plan with three scenarios and labelled assumptions, approved by Deepan and Sathya.

Inputs needed

TD funding terms and disbursement schedule; current monthly costs; hiring plan draft.

Depends on

T-001

Unlocks

T-005 T-202

T-004Risk registerFounder's Office & Strategy InputW0Mandatory DeepanNot started15-Nov-26

Why now. The plan has known single points of failure: stack decision, vendor progress, entity registration, pricing, and the C#/.NET hire. Naming them early lets you act before they slip.

Instructions

  1. Build a company risk register (likelihood, impact, owner, mitigation, trigger date), seeded with the gaps listed in this playbook.
  2. Deepan Rate each risk and assign owners.
  3. Team Review the top five every week.

Done when

Register live with owners; top five reviewed weekly.

Inputs needed

Founder's list of worries; vendor status; funding status.

Depends on

T-001

T-005Financial modelFundraising & Investor Relations InputW0Mandatory DeepanIn progress15-Nov-26

Why now. The financial model is how investors and the founder see runway. It must use one set of locked numbers so documents stop contradicting each other.

Instructions

  1. Build P&L, cash flow, burn and runway with unit-economics tabs and scenario toggles; label all estimates.
  2. Sathya Validate accounting treatment.
  3. Deepan Lock assumptions.

Done when

Model validated by Sathya and used as the single source for every document.

Inputs needed

Current price assumptions (update once T-077 locks pricing); cost base; TD terms.

Depends on

T-003

Unlocks

T-007 T-016 T-077 T-163 T-166

T-006Stack evaluationEngineering InputW0Mandatory KrishnaIn progress07-Nov-26

Why now. The stack is a technology input that every engineering task depends on. A one-week spike replaces opinion with evidence: build the same thin slice (agent event capture to API to stored event) in .NET and in the Python hybrid.

Instructions

  1. Write both thin slices in the code workspace; measure footprint, effort and Windows packaging fit; document migration risk.
  2. Krishna Run the agent slice on a real Windows machine.
  3. Feed results into the decision memo (T-002).

Done when

Benchmarks and a recommendation attached to the decision memo.

Inputs needed

Lenin's Python proposal; .NET developer availability.

Depends on

T-002

Unlocks

T-031

T-007Budget & burn trackerFinance & Accounts InputW0Mandatory DeepanNot started15-Nov-26

Why now. Capital is the first input. TD's ₹1.5 Cr must be tracked from day one against the plan.

Instructions

  1. Build budget vs actuals with runway alerts.
  2. Deepan Provide actuals monthly.

Done when

Tracker updated monthly.

Inputs needed

Model; bank actuals.

Depends on

T-005

Unlocks

T-087 T-106 T-180

T-008Incorporation & compliance calendarLegal & Company Secretarial InputW0Mandatory SathyaIn progress15-Nov-26

Why now. The new Teemly entity is the root dependency. Share allotment to TD and Naveen, GST invoices, customer contracts, the code-signing certificate, Partner Center and trademark filing all need it.

Instructions

  1. Build the incorporation checklist and post-incorporation compliance calendar.
  2. Sathya File and complete registrations.

Done when

Entity incorporated; registrations complete.

Inputs needed

Founder and shareholder details; registered address.

Depends on

None. Can start now.

Unlocks

T-009 T-010 T-011 T-013 T-014 T-048 T-073 T-104 T-114 T-116

T-009Cap table & dilution scenariosFundraising & Investor Relations InputW0Mandatory DeepanIn progress15-Nov-26

Why now. Shares can only be allotted once the new Teemly entity exists and the cap table is final. Introducer equity must stay structurally separate from investor and operating equity.

Instructions

  1. Build the cap table with pre/post-money, ESOP pool and dilution scenarios, introducer stake on its own line.
  2. Sathya Validate against the shareholding pattern and filings.

Done when

Final cap table matches filed shareholding pattern.

Inputs needed

Incorporation details; TD and Naveen terms; ESOP pool intent.

Depends on

T-008

Unlocks

T-012 T-166 T-167

T-010Tax, GST, TDS, payroll, auditFinance & Accounts InputW0Mandatory SathyaNot started15-Nov-26

Why now. Statutory compliance for the new entity (GST, TDS, payroll, audit) is non-negotiable and has fixed dates.

Instructions

  1. Build compliance calendar and document checklists.
  2. Sathya Execute and file.

Done when

Calendar live; no missed filing.

Inputs needed

Incorporation details.

Depends on

T-008

T-011Board resolutions & minutesLegal & Company Secretarial InputW0Mandatory SathyaNot started15-Nov-26

Why now. Share allotment and bank mandates require board resolutions.

Instructions

  1. Draft resolutions, minutes, registers.
  2. Directors Sign; Sathya files.

Done when

Allotment resolutions signed and filed.

Inputs needed

Board decisions.

Depends on

T-008

T-012Term sheet & SHA reviewLegal & Company Secretarial InputW0Mandatory DeepanIn progress15-Nov-26

Why now. Terms signed now shape control and future rounds.

Instructions

  1. Plain-language summary and issue list.
  2. Counsel Negotiate and finalise.

Done when

SHA signed.

Inputs needed

Term sheet; SHA draft.

Depends on

T-009

T-013Vendor & developer agreementsLegal & Company Secretarial InputW0Mandatory DeepanNot started15-Nov-26

Why now. Without written IP assignment, Teemly may not own the code its vendors write. This must be signed before more code is delivered.

Instructions

  1. Draft SOW-backed agreements with IP assignment, confidentiality, source-code handover and milestones.
  2. Counsel Review; both parties sign.

Done when

Signed agreements with IP assignment for every vendor.

Inputs needed

Vendor commercial terms.

Depends on

T-008

Unlocks

T-027

T-014Employment documentsLegal & Company Secretarial InputW0Mandatory DeepanNot started15-Nov-26

Why now. The C#/.NET hire and every team member need contracts with IP and confidentiality clauses.

Instructions

  1. Draft offer letter, contract and IP agreement.
  2. Counsel Review.

Done when

Templates approved and used.

Inputs needed

Role terms.

Depends on

T-008

Unlocks

T-053

T-015Hiring plan & org designPeople & Talent (HR) InputW0Mandatory DeepanIn progress15-Nov-26

Why now. People are the binding input for the agent build. Investors also asked for the hiring plan.

Instructions

  1. Draft role sequence, org chart and cost per role tied to milestones.
  2. Deepan Approve.

Done when

Plan approved and shared with investors.

Inputs needed

Delivery model decision; budget.

Depends on

T-001

Unlocks

T-016 T-017

T-016Use of funds & hiring planFundraising & Investor Relations InputW0Mandatory DeepanIn progress15-Nov-26

Why now. Investors asked for a hiring plan alongside sales and marketing plans. Use of funds turns the ₹1.5 Cr into month-wise spend tied to milestones.

Instructions

  1. Draft month-wise use of funds and hiring sequence linked to the delivery and launch milestones.
  2. Deepan Commit and submit to investors.

Done when

Plan submitted to investors.

Inputs needed

Hiring plan; vendor costs; GTM budget.

Depends on

T-005 T-015

T-017Job descriptionsPeople & Talent (HR) InputW0Mandatory DeepanIn progress15-Nov-26

Why now. The C#/.NET developer (backend + desktop agent) is the most urgent hire.

Instructions

  1. Write JD.
  2. Deepan Share in known circle and on job boards.

Done when

JD live.

Inputs needed

Role scope.

Depends on

T-015

Unlocks

T-018 T-049

T-018Interview kitsPeople & Talent (HR) InputW0Mandatory DeepanNot started15-Nov-26

Why now. Structured interviews hire faster and better.

Instructions

  1. Questions, take-home task, scoring rubric.
  2. Krishna Calibrate.

Done when

Kit ready before first interview.

Inputs needed

JD.

Depends on

T-017

Unlocks

T-019

T-019Resume screeningPeople & Talent (HR) InputW0Mandatory DeepanNot started15-Nov-26

Why now. Screening against a rubric saves founder time.

Instructions

  1. Score CVs with reasons.
  2. Deepan Shortlist; check for bias.

Done when

Shortlist within 48 hours of each batch.

Inputs needed

CVs.

Depends on

T-018

Unlocks

T-020

T-020Interviews & hiring decisionsPeople & Talent (HR) InputW0Mandatory DeepanNot started15-Nov-26

Why now. Hiring decisions are human.

Instructions

  1. Debrief summaries.
  2. Deepan Interview, decide, close.

Done when

C#/.NET developer accepted offer by mid-November.

Inputs needed

Shortlist.

Depends on

T-019

Unlocks

T-053

T-021Vendor evaluationDelivery, Operations & Vendor Management InputW0Mandatory KrishnaIn progress15-Nov-26

Why now. Vendor progress is a concern. A scorecard decides objectively whether to continue, add a vendor, or bring work in-house.

Instructions

  1. Build scorecard (speed, quality, stack fit, cost, IP terms) and compare options.
  2. Deepan Choose.

Done when

Vendor decision recorded.

Inputs needed

Vendor proposals; delivery history.

Depends on

T-002

T-022PRDs & module specsProduct Management TransformationW0Mandatory KrishnaIn progress15-Nov-26

Why now. Transformation starts with a precise description of the value to build. Module specs for Dashboard, Teams, Attendance, Reports and Admin Control Centre are the input to design, architecture and vendor SOWs.

Instructions

  1. Write one spec per module: purpose, users, rules, edge cases, permissions, non-goals, org-level-first defaults.
  2. Krishna Resolve open questions with Deepan.
  3. Mark every item as Phase 1 or later (feeds T-024).

Done when

Signed-off module specs.

Inputs needed

Existing Teemly documents; Super Admin spec; client Admin design in Figma; six report mockups.

Depends on

T-001

Unlocks

T-023 T-024 T-029 T-030 T-031 T-033 T-034 T-036 T-148

T-023Super Admin portal specProduct Management TransformationW0Mandatory DeepanIn review15-Nov-26

Why now. The Super Admin spec is the baseline for design and development and is already drafted; the Super Admin screens SA-00 to SA-09 are designed in Figma. Keep spec and design in sync.

Instructions

  1. Reconcile spec against the 59 designed frames; list mismatches.
  2. Deepan Approve changes.

Done when

Spec and design match; changes logged.

Inputs needed

Current spec; Figma file.

Depends on

T-022

Unlocks

T-028 T-030

T-024Roadmap & prioritisationProduct Management TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. Building from the foundation in October for a December delivery leaves about nine weeks. Past experience shows a 6-9 month scope does not fit in 12 weeks. Phase 1 must be cut to what delivers the core value: agent capture, the six reports, client admin, consent and privacy.

Instructions

  1. Score every feature with RICE and estimate effort with the vendor's input.
  2. Propose a Phase 1 line that fits the delivery date with 20% buffer.
  3. Deepan + Krishna Decide the line; move the rest to Phase 2.

Done when

Written Phase 1 scope that the vendor confirms is achievable by end of December.

Inputs needed

Module specs; vendor capacity; stack decision.

Depends on

T-002 T-022

Unlocks

T-025 T-027 T-028

T-025Delivery plan & GanttDelivery, Operations & Vendor Management InputW0Mandatory PrinishaNot started15-Nov-26

Why now. Time is an input. A dependency-aware plan shows the real critical path to end of December.

Instructions

  1. Build the milestone plan with dependencies and a FigJam Gantt.
  2. Krishna Commit dates with vendors.

Done when

Baseline plan agreed by all vendors.

Inputs needed

Phase 1 scope; vendor estimates.

Depends on

T-024

Unlocks

T-026 T-042 T-100

T-026Risk & dependency logDelivery, Operations & Vendor Management InputW0Mandatory PrinishaNot started15-Nov-26

Why now. Blockers surface early when someone owns each dependency.

Instructions

  1. Build the log with owners and escalation paths.
  2. Prinisha Escalate and resolve.

Done when

Reviewed weekly.

Inputs needed

Plan.

Depends on

T-025

T-027SOWs & milestone acceptanceDelivery, Operations & Vendor Management InputW0Mandatory KrishnaNot started15-Nov-26

Why now. Clear SOWs with acceptance criteria are how vendors are held to the December date.

Instructions

  1. Draft SOWs with milestones, deliverables, acceptance criteria and payment links.
  2. Krishna Negotiate; Deepan signs.

Done when

Signed SOW per vendor.

Inputs needed

Phase 1 scope; agreement terms.

Depends on

T-013 T-024

Unlocks

T-047 T-059 T-062 T-072

T-028User stories & acceptance criteriaProduct Management TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. Vendors build exactly what is written. Stories with Given/When/Then criteria remove ambiguity and become the acceptance test for each milestone.

Instructions

  1. Write stories per module with acceptance criteria, ordered by dependency.
  2. Krishna Groom with the vendor team; confirm estimates.

Done when

Full Phase 1 backlog accepted by the vendor.

Inputs needed

Phase 1 scope; module specs.

Depends on

T-023 T-024

Unlocks

T-056 T-064 T-065 T-088

T-029User flows & journeysUI/UX Design TransformationW0Mandatory KevinNot started15-Nov-26

Why now. Flows show where users drop out before anyone draws screens: agent install, consent, first report, drill-down.

Instructions

  1. Draw each flow in FigJam with decision points and error paths.
  2. Kevin Review edge cases with Krishna.

Done when

Approved flows for every Phase 1 journey.

Inputs needed

Module specs.

Depends on

T-022

Unlocks

T-054

T-030Information architectureUI/UX Design TransformationW0Mandatory KevinIn progress15-Nov-26

Why now. A shared navigation model across Client Admin, Super Admin and Employee self-view prevents rework when screens multiply.

Instructions

  1. Produce sitemaps and navigation for all three portals in FigJam.
  2. Kevin + Deepan Approve.

Done when

Approved IA for all three portals.

Inputs needed

Specs; existing sidebars.

Depends on

T-022 T-023

Unlocks

T-054

T-031System architecture & ADRsEngineering TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. Architecture fixes the shape of everything built in the next nine weeks: agent, ingestion, multi-tenant backend, three portals.

Instructions

  1. Draft component, data-flow and sequence diagrams and one ADR per key decision (tenancy, event transport, storage, auth).
  2. Vendor lead Challenge and sign off.

Done when

Signed-off architecture pack and ADRs.

Inputs needed

Stack decision; module specs.

Depends on

T-006 T-022

Unlocks

T-032 T-055 T-056 T-070 T-098

T-032Cloud architecture & sizingDevOps, Cloud & IT InputW0Mandatory KrishnaNot started15-Nov-26

Why now. Infrastructure is an input: it must exist before ingestion can be tested, and its cost per seat shapes margins.

Instructions

  1. Design dev/staging/production, size for launch volumes, estimate cost per 100 seats.
  2. Deepan Approve budget and provider.

Done when

Approved environment design and budget.

Inputs needed

Architecture; expected seat volumes; provider preference.

Depends on

T-031

Unlocks

T-052

T-033Metric definitionsData, Analytics & AI TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. The six reports are Teemly's core value. Each metric needs a precise, defensible definition before anyone builds a query or a chart.

Instructions

  1. Define Work Pulse, Focus Score, Burnout & Wellbeing signals, Tool Intelligence, Attendance and Team Leaderboard: formula, inputs, thresholds, known limitations.
  2. Krishna Review with Deepan; check all metrics are team or org level by default.

Done when

Versioned metric dictionary approved.

Inputs needed

Report mockups; domain input from pilot prospects.

Depends on

T-022

Unlocks

T-034 T-068 T-069 T-075

T-034Report logic specsProduct Management TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. Turns metric definitions into build-ready report specs: data sources, aggregation windows, filters, drill-downs and edge cases.

Instructions

  1. Write a spec per report with worked examples and test data.
  2. Krishna Validate with domain experts or pilot prospects.

Done when

Six report specs with worked examples, approved.

Inputs needed

Metric dictionary; agent event schema.

Depends on

T-022 T-033

Unlocks

T-055 T-081

T-035DPDP Act gap assessmentSecurity, Privacy & Compliance TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. Privacy is part of the product, not a document added later. The DPDP assessment sets requirements for consent, retention and data rights before design and build lock in. Retention periods also differ between documents (30-day rolling vs plan-based 30/90/180 days) and must be settled here.

Instructions

  1. Map data flows to the DPDP Act and Rules; list gaps and product requirements.
  2. Counsel Legal review.
  3. Krishna Feed requirements into specs.

Done when

Assessment signed off; retention policy decided.

Inputs needed

Data flows; agent capture list; retention intent.

Depends on

None. Can start now.

Unlocks

T-036 T-078 T-117 T-147 T-185 T-191

T-036Privacy-by-design reviewProduct Management TransformationW0Mandatory KrishnaNot started15-Nov-26

Why now. Org-level-first, consent and employee-controlled blur are the positioning. Catching violations at spec time avoids rework after build.

Instructions

  1. Review each feature against org-level-first, consent, blur, retention and DPDP rules; list violations and fixes.
  2. Krishna + Deepan Decide borderline cases.

Done when

Every Phase 1 feature passes the checklist.

Inputs needed

Module specs; DPDP assessment.

Depends on

T-022 T-035

Unlocks

T-060

T-037Design tokensUI/UX Design LeverageW0Mandatory KevinIn progress15-Nov-26

Why now. Tokens make every later screen consistent and cheap to change, which is leverage. The Super Admin file already has a Foundations board (blue accent); align Client Admin and Employee views to the same tokens.

Instructions

  1. Audit tokens across Super Admin and Client Admin files; propose one shared set of Figma variables with light and dark modes.
  2. Kevin + Deepan Approve palette and type.
  3. Bind both files to the shared variables.

Done when

One token set used by all portals.

Inputs needed

Super Admin Foundations page; 8-Pillar brand colours.

Depends on

None. Can start now.

Unlocks

T-079 T-090 T-094

T-038Google Drive organisationDelivery, Operations & Vendor Management LeverageW0Mandatory PrinishaNot started15-Nov-26

Why now. One organised Drive is the single source of truth for the team and the base of the data room.

Instructions

  1. Propose folder structure, naming and index.
  2. Prinisha Approve; move sensitive files.

Done when

Drive reorganised with index.

Inputs needed

Current files.

Depends on

None. Can start now.

Unlocks

T-039

T-039Data room structureFundraising & Investor Relations InputW0Mandatory DeepanIn progress15-Nov-26

Why now. The cap table, shareholding pattern and data room are being closed with TD and Naveen now. Capital is the first input; a clean data room shortens closing.

Instructions

  1. Create the folder structure and index in Google Drive with a checklist of required documents and their status.
  2. Produce a gap list of missing or outdated items.
  3. Deepan Upload originals; set access per investor.

Done when

Index complete, gaps closed, investor access granted.

Inputs needed

Incorporation documents, cap table, financials, contracts, IP documents.

Depends on

T-038

Unlocks

T-040

T-040Due-diligence responsesFundraising & Investor Relations InputW0Mandatory DeepanNot started15-Nov-26

Why now. Diligence questions block closing. Fast, consistent answers drawn from one set of facts avoid rework.

Instructions

  1. Draft answers from existing documents; flag anything unverifiable.
  2. Deepan Verify facts and provide missing records.

Done when

All questions answered and verified.

Inputs needed

Investor questionnaire; data room.

Depends on

T-039

T-041Personas & jobs-to-be-doneProduct Management FeedbackW0Mandatory KrishnaNot started15-Nov-26

Why now. Specs and marketing both need to know who buys (founder, HR head, ops manager) and who is affected (employees). Draft from what is known; validate in interviews.

Instructions

  1. Draft buyer and user personas, jobs-to-be-done and buying-committee map, labelled as hypotheses.
  2. Krishna Mark which claims need evidence.

Done when

Persona set marked with what is assumed vs evidenced.

Inputs needed

Pipeline client profiles; earlier ICP work.

Depends on

None. Can start now.

Unlocks

T-076 T-095 T-102 T-134

T-042Weekly status reportsDelivery, Operations & Vendor Management FeedbackW0Mandatory PrinishaNot started15-Nov-26

Why now. Weekly evidence of progress is the fastest feedback loop on the build.

Instructions

  1. Compile status from updates every week (can run as a scheduled task).
  2. Prinisha Collect updates.

Done when

Report every week.

Inputs needed

Team updates.

Depends on

T-025

Unlocks

T-045 T-099

T-043Meeting prep briefsFounder's Office & Strategy InputW0Launch-critical DeepanNot started15-Nov-26

Why now. Founder time is a scarce input. A one-page brief before investor, vendor and client meetings makes each meeting decide something.

Instructions

  1. Prepare a brief: background, goal, three questions to ask, likely objections, decision needed.
  2. Deepan Read for two minutes before the meeting; add relationship context.

Done when

Brief exists for every investor, vendor and client meeting.

Inputs needed

Meeting purpose, attendees, any prior emails or notes.

Depends on

None. Can start now.

T-044Meeting notes to action itemsFounder's Office & Strategy InputW0Launch-critical DeepanNot started15-Nov-26

Why now. Decisions that are not written down get re-made. Turning notes into owners and dates keeps the plan moving.

Instructions

  1. Deepan Paste notes or a transcript within 24 hours.
  2. Extract decisions, actions, owners and due dates; add actions to the risk/dependency log where relevant.
  3. Include open actions in the next weekly update.

Done when

Every key meeting has a written action list with owners.

Inputs needed

Meeting notes or transcript.

Depends on

None. Can start now.

T-045Weekly founder updateFounder's Office & Strategy InputW0Launch-critical DeepanNot started15-Nov-26

Why now. With vendors, an intern, a new hire and a CA working in parallel, one weekly update keeps everyone aligned on the same priorities.

Instructions

  1. Compile a draft every Friday: progress against OKRs, decisions, risks, asks.
  2. Deepan Edit tone and priorities; send.

Done when

Update sent every week without a gap.

Inputs needed

Weekly status report; KPI dashboard; decisions from the week.

Depends on

T-001 T-042

T-046Tool stack & access policyDevOps, Cloud & IT InputW0Launch-critical KrishnaNot started15-Nov-26

Why now. Vendors and new hires need the right access on day one, and access must be removed on exit.

Instructions

  1. Build the tool stack list, access matrix and joiner/leaver checklist.
  2. Krishna Administer accounts.

Done when

Access matrix live; checklist used for every change.

Inputs needed

Tool list; people list.

Depends on

None. Can start now.

Unlocks

T-105

T-047Vendor payment trackerFinance & Accounts InputW0Launch-critical PrinishaNot started15-Nov-26

Why now. Paying vendors only against accepted milestones protects cash and timeline.

Instructions

  1. Build milestone-linked payment tracker.
  2. Deepan Approve and pay.

Done when

Every payment linked to an accepted milestone.

Inputs needed

SOWs.

Depends on

T-027

T-048NDAsLegal & Company Secretarial InputW0Launch-critical DeepanNot started15-Nov-26

Why now. Vendors, candidates and prospects will see confidential material.

Instructions

  1. Mutual and one-way NDA templates.
  2. Counsel Approve template.

Done when

Templates in use.

Inputs needed

Entity details.

Depends on

T-008

T-049Careers page & hiring postsPeople & Talent (HR) InputW0Launch-critical DeepanNot started15-Nov-26

Why now. A careers page and hiring posts widen the funnel beyond the known circle.

Instructions

  1. Careers copy and LinkedIn hiring posts.
  2. Deepan Post.

Done when

Posts live.

Inputs needed

JDs.

Depends on

T-017

T-050Vendor relationshipsDelivery, Operations & Vendor Management InputW0Launch-critical DeepanNot started15-Nov-26

Why now. Vendors deliver for people they trust; relationships stay human.

Instructions

  1. Meeting prep.
  2. Deepan + Krishna Manage expectations.

Done when

Weekly vendor check-ins held.

Inputs needed

Meeting schedule.

Depends on

None. Can start now.

T-051Meeting minutes & follow-upsDelivery, Operations & Vendor Management InputW0Launch-critical PrinishaNot started15-Nov-26

Why now. Delivery meetings need written decisions and owners.

Instructions

  1. Minutes and action tracking.
  2. Prinisha Share notes.

Done when

Minutes for every delivery meeting.

Inputs needed

Notes.

Depends on

None. Can start now.

T-052Infrastructure as codeDevOps, Cloud & IT InputW1Mandatory Pune infra vendorNot started31-Dec-26

Why now. Infrastructure as code makes environments reproducible and portable between vendors.

Instructions

  1. Write Terraform/Bicep, Dockerfiles and configs.
  2. Vendor Apply with real credentials.

Done when

Staging environment created from code.

Inputs needed

Approved design; cloud credentials (held by the team).

Depends on

T-032

Unlocks

T-058 T-063 T-144 T-145

T-053Offer & onboarding packsPeople & Talent (HR) InputW1Mandatory DeepanNot started31-Dec-26

Why now. A good first week makes a new hire productive in days, not weeks.

Instructions

  1. Offer letter, welcome pack, 30-60-90 plan.
  2. Deepan Personal welcome.

Done when

New hire productive in week one.

Inputs needed

Signed contract.

Depends on

T-014 T-020

T-054WireframesUI/UX Design TransformationW1Mandatory KevinNot started31-Dec-26

Why now. Wireframes are the cheapest place to fix layout problems on the Client Admin and Employee views still to be designed.

Instructions

  1. Build low-fidelity wireframes in Figma for every remaining Phase 1 screen.
  2. Kevin Pick directions with Deepan.

Done when

Wireframes approved for every remaining Phase 1 screen.

Inputs needed

Flows; IA.

Depends on

T-029 T-030

Unlocks

T-080 T-108

T-055Database designEngineering TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. The schema determines report speed and retention compliance.

Instructions

  1. Design the multi-tenant schema, ER diagram, indexes and retention jobs.
  2. Vendor Review performance and migration plan.

Done when

Schema approved and migrations in repo.

Inputs needed

Architecture; report specs; retention policy.

Depends on

T-031 T-034

Unlocks

T-057 T-068

T-056API contractsEngineering TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. Frozen API contracts let agent, backend and frontend teams work in parallel without blocking each other.

Instructions

  1. Write OpenAPI specs for portal, ingestion and admin APIs, with examples.
  2. Krishna + vendor Review and freeze.

Done when

Contracts frozen and published.

Inputs needed

Architecture; user stories.

Depends on

T-028 T-031

Unlocks

T-057 T-058 T-059 T-084

T-057Core servicesEngineering TransformationW1Mandatory Dev vendorNot started31-Dec-26

Why now. Auth, RBAC, tenants, teams and policies are the base every feature sits on.

Instructions

  1. Write services and tests; open PRs.
  2. Vendor Review, integrate, own security review.

Done when

Core services merged with tests passing.

Inputs needed

Contracts; schema.

Depends on

T-055 T-056

Unlocks

T-085 T-091 T-190

T-058Event ingestion pipelineEngineering TransformationW1Mandatory Dev vendorNot started31-Dec-26

Why now. Ingestion of the 60-second event stream is the pipe all value flows through; it must not lose data.

Instructions

  1. Build receive, validate, queue and store with idempotency and back-pressure.
  2. Vendor Load-test on real infrastructure; tune.

Done when

Pipeline handles target load with no loss.

Inputs needed

Contracts; infrastructure.

Depends on

T-052 T-056

Unlocks

T-121

T-059Agent coreEngineering TransformationW1Mandatory C#/.NET developer (hire)Not started31-Dec-26

Why now. The OS-level agent is the source of every signal. Its footprint and reliability decide whether IT teams accept it.

Instructions

  1. Write the Windows service: app/URL activity, idle detection, batching, offline cache.
  2. Developer Build and test on real Windows machines.

Done when

Agent runs a full day on test machines within footprint targets.

Inputs needed

Contracts; stack decision; Windows test machines.

Depends on

T-027 T-056

Unlocks

T-060 T-074

T-060Screenshot & privacy controlsEngineering TransformationW1Mandatory C#/.NET developer (hire)Not started31-Dec-26

Why now. Employee-controlled blur and consent gating are what make Teemly trustworthy rather than intrusive.

Instructions

  1. Implement capture with blur, consent gating and policy sync.
  2. Developer Device test; Krishna privacy review.

Done when

Privacy controls pass the privacy-by-design checklist.

Inputs needed

Privacy rules; consent copy.

Depends on

T-036 T-059

T-061Code reviewEngineering TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. With vendor and in-house code merging fast, review is the quality gate that protects the December date.

Instructions

  1. Review every PR for bugs, security and performance with suggested fixes.
  2. Krishna Make merge decisions.

Done when

No PR merged without review.

Inputs needed

Repository access (attach in this session).

Depends on

None. Can start now.

T-062Vendor code auditsEngineering TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. Independent review of vendor deliveries against acceptance criteria protects money and timeline.

Instructions

  1. Audit code and features against criteria; list gaps.
  2. Krishna Act on findings with the vendor.

Done when

Each milestone has an audit report before payment.

Inputs needed

Milestone delivery; SOW criteria.

Depends on

T-027

Unlocks

T-072

T-063CI/CD pipelinesDevOps, Cloud & IT TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. Automated build, test and deploy is what makes weekly releases safe.

Instructions

  1. Write GitHub Actions for build, test, security scan and deploy to staging.
  2. Krishna Approve production gate.

Done when

Every merge deploys to staging automatically.

Inputs needed

Repository; environments.

Depends on

T-052

Unlocks

T-066 T-146

T-064Test strategy & planQA & Testing TransformationW1Mandatory BharathNot started31-Dec-26

Why now. A test strategy decides what "done" means for the December delivery.

Instructions

  1. Write scope, levels, environments, entry/exit criteria.
  2. Krishna Approve.

Done when

Approved test plan.

Inputs needed

Phase 1 stories.

Depends on

T-028

Unlocks

T-065 T-066 T-067

T-065Test casesQA & Testing TransformationW1Mandatory BharathNot started31-Dec-26

Why now. Test cases from stories make acceptance objective.

Instructions

  1. Generate positive, negative and edge cases per story.
  2. Bharath Review coverage.

Done when

Every Phase 1 story has test cases.

Inputs needed

Stories.

Depends on

T-028 T-064

Unlocks

T-093 T-120

T-066Unit & integration testsQA & Testing TransformationW1Mandatory Dev teamNot started31-Dec-26

Why now. Unit and integration tests catch regressions as the vendor speeds up.

Instructions

  1. Write tests alongside features.
  2. Developers Keep them green in CI.

Done when

Agreed coverage on core services.

Inputs needed

Codebase; CI.

Depends on

T-063 T-064

Unlocks

T-111

T-067Bug triage & reportsQA & Testing TransformationW1Mandatory BharathNot started31-Dec-26

Why now. A clean, prioritised bug list keeps the team on what matters for release.

Instructions

  1. De-duplicate, prioritise and write repro steps.
  2. Bharath Final severity call.

Done when

No untriaged bugs older than 24 hours.

Inputs needed

Bug reports.

Depends on

T-064

T-068SQL & data modelsData, Analytics & AI TransformationW1Mandatory Dev vendorNot started31-Dec-26

Why now. Queries and aggregation tables turn raw events into the six reports.

Instructions

  1. Write queries, views and aggregation jobs with test fixtures.
  2. Vendor Review performance on realistic volumes.

Done when

Each report's numbers match the worked examples.

Inputs needed

Metric dictionary; schema.

Depends on

T-033 T-055

Unlocks

T-086 T-091 T-187 T-191 T-213

T-069Activity classificationData, Analytics & AI TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. Productivity classification feeds most reports. Start rules-first, then add ML where evidence supports it.

Instructions

  1. Build a rules engine with per-org overrides and an ML prototype; report accuracy.
  2. Krishna Provide labelled data; sign off accuracy.

Done when

Classification meets agreed accuracy on test set.

Inputs needed

App/URL lists by role; labelled examples.

Depends on

T-033

Unlocks

T-171

T-070Threat modellingSecurity, Privacy & Compliance TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. A threat model before build focuses security effort on what attackers would target.

Instructions

  1. STRIDE model for agent, ingestion and portals with mitigations.
  2. Krishna Engineering review.

Done when

Mitigations added to backlog.

Inputs needed

Architecture.

Depends on

T-031

Unlocks

T-071 T-137

T-071Secure code reviewSecurity, Privacy & Compliance TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. Secure code review catches OWASP issues before customers' data is at risk.

Instructions

  1. Review PRs and dependencies.
  2. Developers Fix and verify.

Done when

No open high-severity findings at release.

Inputs needed

Repository.

Depends on

T-070

Unlocks

T-111

T-072Vendor deliverable reviewDelivery, Operations & Vendor Management TransformationW1Mandatory KrishnaNot started31-Dec-26

Why now. Accept or reject each milestone on evidence before payment.

Instructions

  1. Check deliverables against SOW, tests and documentation.
  2. Krishna Accept or reject.

Done when

Every milestone formally accepted or rejected.

Inputs needed

Delivery; audit report.

Depends on

T-027 T-062

T-073Code signing & Microsoft StoreEngineering TransmissionW1Mandatory DeepanNot started15-Dec-26

Why now. Lead-time item. An installer without a trusted signature triggers Windows warnings that IT teams reject. Code-signing certificates and Microsoft Partner Center company accounts need a registered organisation and verification that can take weeks.

Instructions

  1. Prepare the certificate options, Partner Center checklist and Store listing text.
  2. Deepan Buy the certificate, complete identity verification, open the Partner Center account.

Done when

Certificate issued and Partner Center account verified before the December release.

Inputs needed

Teemly incorporation documents; company email domain.

Depends on

T-008

Unlocks

T-074

T-074Installer & auto-updateEngineering TransformationW1Mandatory C#/.NET developer (hire)Not started31-Dec-26

Why now. Customers deploy to many machines at once; silent install and auto-update decide time-to-value.

Instructions

  1. Write MSI/MSIX packaging, silent install switches and update channel.
  2. Developer Package and test rollout on Windows.

Done when

Silent install and update tested on 3+ Windows versions.

Inputs needed

Signed build; packaging choice.

Depends on

T-059 T-073

Unlocks

T-110 T-118

T-075Synthetic demo datasetsData, Analytics & AI TransmissionW1Mandatory KrishnaNot started31-Dec-26

Why now. Realistic demo data powers tests, screenshots and sales demos before real customers exist.

Instructions

  1. Generate org datasets for IT services, BPO, agency and accounting.
  2. Krishna Approve scenarios.

Done when

Demo datasets loaded in staging.

Inputs needed

Metric dictionary; vertical scenarios.

Depends on

T-033

Unlocks

T-113 T-122

T-076ICP & segmentationSales & Business Development TransmissionW1Mandatory NaveenIn progress31-Dec-26

Why now. Every reach activity (website, content, outbound, ads) depends on who exactly we are trying to reach. Sharpen the ICP before producing any GTM asset.

Instructions

  1. Define ICP by vertical (IT services, digital agencies, BPO/KPO, accounting), size band, pains and trigger events; rank segments by reachability and value.
  2. Naveen + Deepan Validate against real deals; pick the launch segment.

Done when

One-page ICP with a chosen launch segment.

Inputs needed

Pipeline client profiles; persona hypotheses; interview insights as they arrive.

Depends on

T-041

Unlocks

T-095 T-112 T-123 T-124 T-127 T-136 T-139 T-141 T-157 T-179 T-180

T-077Pricing analysisFinance & Accounts ConversionW1Mandatory DeepanNot started31-Dec-26

Why now. Three different price sets exist: the investor deck (₹499 / ₹699 / ₹899, $5 / $7 / $11, Enterprise floor ₹750+ which sits below Premium), the Super Admin sample data (₹299 / ₹499 / ₹749), and earlier materials (₹599 / ₹999 / ₹1,499). Website, proposals, ROI calculators and the financial model cannot be finished until one set is locked.

Instructions

  1. Compare the three sets on margin, competitiveness and ARPU; recommend one with plan limits and the Enterprise floor fixed.
  2. Deepan Lock pricing and plan limits.
  3. Update every document that carries a price.

Done when

One locked price list used everywhere.

Inputs needed

Competitor prices; margin model; any early interview evidence (do not wait for the full research round).

Depends on

T-005

Unlocks

T-114 T-115 T-139 T-142

T-078Privacy notice & consent textsSecurity, Privacy & Compliance RetentionW1Mandatory KrishnaNot started31-Dec-26

Why now. Employees must see clear consent copy inside the agent and portal. The agent cannot ship without it.

Instructions

  1. Draft privacy policy, employee consent notice and in-agent consent copy.
  2. Counsel Sign off.

Done when

Approved texts in the product.

Inputs needed

DPDP assessment.

Depends on

T-035

Unlocks

T-140 T-149 T-213

T-079Component libraryUI/UX Design LeverageW1Mandatory KevinIn progress31-Dec-26

Why now. The Super Admin file has a strong component set. Reusing it across portals is the main design leverage.

Instructions

  1. Publish the components as a shared library; add any missing pieces needed by Client Admin and Employee views (filters, report cards, consent banners).
  2. Kevin Review consistency.

Done when

Shared library used by every portal file.

Inputs needed

Super Admin Components page.

Depends on

T-037

Unlocks

T-080 T-081 T-083 T-097 T-189

T-080High-fidelity screensUI/UX Design TransformationW1Mandatory KevinIn progress31-Dec-26

Why now. Super Admin (SA-00 to SA-09) is designed. The Client Admin portal and the Employee self-view must reach the same standard before the vendor builds them.

Instructions

  1. Build high-fidelity screens module by module in Figma using the shared library.
  2. Kevin + Deepan Art-direct and polish each module before moving on.
  3. Note The Figma Starter plan hit its usage limit during the Super Admin build; upgrading the plan removes this bottleneck.

Done when

All Phase 1 screens across three portals designed and approved.

Inputs needed

Wireframes; shared library; specs.

Depends on

T-054 T-079

Unlocks

T-082 T-083 T-089 T-122

T-081Report & chart componentsUI/UX Design TransformationW1Mandatory KevinNot started31-Dec-26

Why now. The report charts are what customers pay for. They need one accessible visual language.

Instructions

  1. Design chart, heatmap and score-card components for the six reports with accessible colour.
  2. Kevin Approve.

Done when

Report component set approved.

Inputs needed

Report specs; mockups.

Depends on

T-034 T-079

Unlocks

T-086

T-082Clickable prototypesUI/UX Design TransformationW1Mandatory KevinNot started31-Dec-26

Why now. A clickable prototype lets sales demo and lets prospects react before the product is live.

Instructions

  1. Link the key flows (sign-in to first report, report drill-down).
  2. Kevin Wire complex interactions; run two usability sessions.

Done when

Demo prototype used in at least two prospect sessions.

Inputs needed

Approved screens.

Depends on

T-080

Unlocks

T-112

T-083Design to codeUI/UX Design TransformationW1Mandatory BharathNot started31-Dec-26

Why now. Converting approved frames directly into React components that reuse tokens shortens the build.

Instructions

  1. Generate components from Figma that reuse project tokens; open a PR.
  2. Bharath/vendor Review and integrate.

Done when

Components merged for each module.

Inputs needed

Approved frames; repository access.

Depends on

T-079 T-080

Unlocks

T-084

T-084UI components & pagesEngineering TransformationW1Mandatory BharathNot started31-Dec-26

Why now. The portals are where customers experience value.

Instructions

  1. Build pages for each module; open PRs.
  2. Bharath/vendor Review and integrate.

Done when

All Phase 1 pages built.

Inputs needed

Components from Figma; contracts.

Depends on

T-056 T-083

Unlocks

T-085 T-119 T-170 T-189

T-085Data wiring & formsEngineering TransformationW1Mandatory BharathNot started31-Dec-26

Why now. Pages only work once wired to real APIs with validation and role-aware UI.

Instructions

  1. Wire API calls, state, forms, errors, permissions.
  2. Bharath Integration-test.

Done when

Every page works against staging APIs.

Inputs needed

APIs; pages.

Depends on

T-057 T-084

Unlocks

T-093 T-109 T-151

T-086Report & dashboard UIEngineering TransformationW1Mandatory BharathNot started31-Dec-26

Why now. Report UI is the paid product surface.

Instructions

  1. Build charts, filters, drill-downs and PDF/Excel export.
  2. Bharath Validate numbers against backend.

Done when

Six reports render correct numbers.

Inputs needed

Report components; data endpoints.

Depends on

T-068 T-081

Unlocks

T-150

T-087Monthly MISFinance & Accounts InputW1Launch-critical DeepanNot started31-Dec-26

Why now. Investors and founders need the same monthly picture.

Instructions

  1. Monthly MIS with commentary.
  2. Sathya Review.

Done when

MIS issued monthly.

Inputs needed

Actuals.

Depends on

T-007

Unlocks

T-101

T-088Backlog hygieneProduct Management TransformationW1Launch-critical KrishnaNot started31-Dec-26

Why now. A clean backlog keeps vendor sprints flowing and stops scope creep.

Instructions

  1. Split, de-duplicate and rewrite tickets weekly (directly once Jira/Linear is connected).
  2. Krishna Run sprint planning.

Done when

Backlog groomed before each sprint.

Inputs needed

Backlog; sprint feedback.

Depends on

T-028

T-089States & responsive variantsUI/UX Design TransformationW1Launch-critical KevinIn progress31-Dec-26

Why now. Empty, loading, error and permission states are where first impressions break.

Instructions

  1. Add states and responsive variants for every Phase 1 screen.
  2. Kevin Spot-check.

Done when

Every screen has its states.

Inputs needed

Approved screens.

Depends on

T-080

T-090Icons & illustrationsUI/UX Design TransformationW1Launch-critical KevinIn progress31-Dec-26

Why now. The Super Admin file uses Phosphor icons; extend the same set rather than mixing styles.

Instructions

  1. Add missing icons and spot illustrations in brand colours.
  2. Kevin Approve.

Done when

Icon set complete for Phase 1.

Inputs needed

Icon needs list.

Depends on

T-037

T-091Jobs & notificationsEngineering TransformationW1Launch-critical Dev vendorNot started31-Dec-26

Why now. Scheduled aggregation, alerts and digests make reports arrive without users asking.

Instructions

  1. Build jobs and notification templates.
  2. Vendor Review and monitor.

Done when

Jobs run on schedule in staging.

Inputs needed

Services; queries.

Depends on

T-057 T-068

T-092Debugging & refactoringEngineering TransformationW1Launch-critical Dev teamNot started31-Dec-26

Why now. Fast root-cause analysis keeps velocity up.

Instructions

  1. Find root cause and write the fix.
  2. Developer Reproduce and verify.

Done when

Fix merged with a regression test.

Inputs needed

Logs, stack traces, repro steps.

Depends on

None. Can start now.

T-093End-to-end browser testsQA & Testing TransformationW1Launch-critical BharathNot started31-Dec-26

Why now. Browser tests protect sign-in, admin flows and reports from breaking unnoticed.

Instructions

  1. Write Playwright suites.
  2. Bharath Maintain test data.

Done when

Critical paths automated in CI.

Inputs needed

Staging; test data.

Depends on

T-065 T-085

T-094Brand guidelinesMarketing TransmissionW1Launch-critical DeepanNot started31-Dec-26

Why now. Every reach asset should look and sound like one company. The 8-Pillar Foundation document already defines the colours and logo; codify them before producing assets.

Instructions

  1. Write brand guidelines (logo use, colour, type, tone of voice, do's and don'ts) and publish as a Design System artifact and PDF.
  2. Deepan Approve.

Done when

Guidelines published and used by all assets.

Inputs needed

8-Pillar Foundation PDF; design tokens.

Depends on

T-037

Unlocks

T-096 T-123 T-128 T-155 T-173 T-179

T-095Website copyMarketing TransmissionW1Launch-critical DeepanIn progress31-Dec-26

Why now. The website is the main reach channel at launch and is being redesigned now as an enterprise-grade, global site.

Instructions

  1. Write copy page by page, starting with home; keep "workforce/organisational intelligence" positioning, never "monitoring".
  2. Deepan Approve messaging page by page.

Done when

Copy approved for all launch pages.

Inputs needed

ICP; positioning; old site teemly.co.

Depends on

T-041 T-076

Unlocks

T-096 T-126

T-096Page designMarketing TransmissionW1Launch-critical KevinIn progress31-Dec-26

Why now. Design follows approved copy so layouts fit the message.

Instructions

  1. Design pages in Figma or on the Design canvas.
  2. Kevin + Deepan Art direction.

Done when

All launch pages designed.

Inputs needed

Approved copy; brand guidelines.

Depends on

T-094 T-095

Unlocks

T-131

T-097Design System referenceUI/UX Design LeverageW1Launch-critical KevinNot started31-Dec-26

Why now. One browsable reference lets developers build consistently without asking.

Instructions

  1. Create the Design System artifact with tokens, components and usage rules.
  2. Kevin Keep current.

Done when

Reference published and linked from the repo.

Inputs needed

Shared library; tokens.

Depends on

T-079

T-098Technical documentationEngineering LeverageW1Launch-critical KrishnaNot started31-Dec-26

Why now. Documentation lets a new hire or a new vendor become productive without the founder.

Instructions

  1. Write READMEs, API docs, architecture docs and onboarding guide.
  2. Krishna Review.

Done when

New developer can set up and ship in two days.

Inputs needed

Architecture; repository.

Depends on

T-031

Unlocks

T-107

T-099Recurring automationsDelivery, Operations & Vendor Management LeverageW1Launch-critical PrinishaNot started31-Dec-26

Why now. Automating the weekly digest, competitor watch and KPI refresh gives founder time back.

Instructions

  1. Set up scheduled tasks.
  2. Prinisha Review outputs.

Done when

Three automations running.

Inputs needed

Report formats.

Depends on

T-042

T-100Company KPI dashboardFounder's Office & Strategy FeedbackW1Launch-critical DeepanNot started31-Dec-26

Why now. The founder needs one view of build progress, burn, hiring and launch readiness to see which pillar is the current constraint.

Instructions

  1. Build a Dashboard with one section per active pillar and the OKR key results.
  2. Krishna/Deepan Supply numbers weekly (a sheet in Drive).
  3. Refresh and highlight anything off track.

Done when

Dashboard live and refreshed weekly.

Inputs needed

Weekly numbers: milestones done, spend, hires, pipeline stage counts.

Depends on

T-001 T-025

Unlocks

T-101 T-162

T-101Monthly investor updateFundraising & Investor Relations InputW1Launch-critical DeepanNot started31-Dec-26

Why now. Monthly reporting to TD is an obligation once money arrives, and builds the trust needed for follow-on capital.

Instructions

  1. Draft on a schedule on the 3rd of each month: highlights, KPIs, lowlights, asks.
  2. Deepan Confirm facts and send.

Done when

Update sent every month.

Inputs needed

Dashboard; MIS; highlights and lowlights.

Depends on

T-087 T-100

T-102Research plan & interview guidesProduct Management FeedbackW1Launch-critical KrishnaNot started31-Dec-26

Why now. The 10 pipeline prospects are the fastest source of evidence for report logic, pricing and onboarding. Interview them while the product is being built.

Instructions

  1. Write interview guides per persona and a short survey.
  2. Krishna/Deepan Schedule and run 8-10 interviews; record with consent.

Done when

8-10 interviews completed with notes.

Inputs needed

Prospect contacts; persona hypotheses.

Depends on

T-041

Unlocks

T-103

T-103Insight synthesisProduct Management FeedbackW1Launch-critical KrishnaNot started31-Dec-26

Why now. Raw notes only help once patterns are visible and fed back into specs, pricing and messaging.

Instructions

  1. Cluster themes, pains and quotes; map each to a spec, pricing or messaging change.
  2. Krishna Validate themes; update specs.

Done when

Insight report with changes applied to specs.

Inputs needed

Interview notes or transcripts.

Depends on

T-102

T-104Trademark searchLegal & Company Secretarial CompoundingW1Launch-critical DeepanNot started31-Dec-26

Why now. The Teemly name is a compounding asset; file before public launch to avoid a forced rename.

Instructions

  1. Preliminary search and class recommendation (software and SaaS classes).
  2. Trademark attorney File.

Done when

Application filed before launch.

Inputs needed

Entity details.

Depends on

T-008

T-105Laptop & device setupDevOps, Cloud & IT InputW1Strengthen KrishnaNot started31-Dec-26

Why now. Standard setup saves days for each new developer.

Instructions

  1. Write setup scripts and checklist.
  2. Team Run on devices.

Done when

New machine ready in under two hours.

Inputs needed

Stack decision.

Depends on

T-046

T-106Expense categorisationFinance & Accounts InputW1Strengthen DeepanNot started31-Dec-26

Why now. Clean categorisation feeds MIS and burn accuracy.

Instructions

  1. Categorise and flag anomalies.
  2. Deepan Reconcile.

Done when

Statements categorised monthly.

Inputs needed

Bank statement exports.

Depends on

T-007

T-107Learning & developmentPeople & Talent (HR) InputW1Strengthen KrishnaNot started31-Dec-26

Why now. A tech onboarding curriculum lets Bharath and new hires grow without senior peers on site.

Instructions

  1. Curricula and training content.
  2. Krishna Deliver.

Done when

Curriculum used for each new hire.

Inputs needed

Docs.

Depends on

T-098

T-108Fast option explorationUI/UX Design TransformationW1Strengthen KevinNot started31-Dec-26

Why now. Comparing two or three directions is faster than iterating on one, for screens where the right layout is not obvious.

Instructions

  1. Produce 2-3 directions side by side on the Design canvas.
  2. Deepan Choose.

Done when

Direction chosen for each contested screen.

Inputs needed

Wireframe of the screen.

Depends on

T-054

T-109Exploratory testing of web portalsQA & Testing TransformationW2Mandatory BharathNot started15-Jan-27

Why now. Exploratory testing finds what scripted tests miss.

Instructions

  1. Click through staging; log bugs with steps and screenshots.
  2. Bharath Confirm and judge UX issues.

Done when

Exploratory pass completed for release.

Inputs needed

Staging access via browser.

Depends on

T-085

Unlocks

T-111

T-110Agent device testingQA & Testing TransformationW2Mandatory C#/.NET developer (hire)Not started15-Jan-27

Why now. The agent must work on the Windows versions and hardware customers use, within footprint limits. This needs real devices.

Instructions

  1. Write the compatibility matrix and test scripts.
  2. Team Run on devices; record CPU and RAM.

Done when

Matrix passed on all target versions.

Inputs needed

Test machines; signed build.

Depends on

T-074

Unlocks

T-111

T-111Release readinessQA & Testing TransformationW2Mandatory KrishnaNot started31-Dec-26

Why now. One go/no-go checklist turns many test activities into one release decision.

Instructions

  1. Compile the checklist and test summary.
  2. Krishna + Deepan Go/no-go decision.

Done when

December release passes go/no-go.

Inputs needed

Test results; open bugs; security review.

Depends on

T-066 T-071 T-109 T-110

Unlocks

T-113 T-143 T-172

T-112Sales deck & demo scriptSales & Business Development ConversionW2Mandatory NaveenNot started15-Jan-27

Why now. The 10 pipeline prospects need a sharp discovery-to-demo story.

Instructions

  1. Build the sales deck and click-by-click demo script.
  2. Naveen Rehearse.

Done when

Deck and script rehearsed.

Inputs needed

Prototype; ICP.

Depends on

T-076 T-082

Unlocks

T-158

T-113Demo environment dataSales & Business Development ConversionW2Mandatory KrishnaNot started15-Jan-27

Why now. Demos on a live tenant with realistic data convert better than slides.

Instructions

  1. Prepare demo tenant data.
  2. Krishna Load into the demo tenant.

Done when

Demo tenant ready.

Inputs needed

Demo datasets; release.

Depends on

T-075 T-111

Unlocks

T-158

T-114Invoice & quote templatesFinance & Accounts ConversionW2Mandatory SathyaNot started15-Jan-27

Why now. Customers cannot pay without compliant invoices in INR and USD.

Instructions

  1. Build invoice and quote templates.
  2. Sathya Confirm format.

Done when

Templates approved.

Inputs needed

Entity and GST details; pricing.

Depends on

T-008 T-077

Unlocks

T-115 T-200

T-115Proposals & quotationsSales & Business Development ConversionW2Mandatory NaveenNot started15-Jan-27

Why now. Proposals turn a good demo into a commitment.

Instructions

  1. Draft client-specific proposals and quotes.
  2. Naveen Approve pricing; send.

Done when

Proposal template used for first deals.

Inputs needed

Pricing; templates.

Depends on

T-077 T-114

Unlocks

T-158

T-116Customer contractsLegal & Company Secretarial ConversionW2Mandatory Legal counselNot started15-Jan-27

Why now. No contract, no paid pilot.

Instructions

  1. Draft SaaS agreement, MSA, SLA and order form.
  2. Counsel Review.

Done when

Contract set approved.

Inputs needed

Pricing; SLA intent.

Depends on

T-008

Unlocks

T-117 T-158 T-160

T-117Data Processing AgreementSecurity, Privacy & Compliance ConversionW2Mandatory Legal counselNot started15-Jan-27

Why now. Business customers need a DPA to sign. No DPA, no paid pilot.

Instructions

  1. Draft DPA with sub-processor list.
  2. Counsel Sign off.

Done when

DPA template approved.

Inputs needed

DPDP assessment; customer contract.

Depends on

T-035 T-116

Unlocks

T-158

T-118Agent deployment guideCustomer Success & Support RetentionW2Mandatory KrishnaNot started15-Jan-27

Why now. No install, no value. IT admins need a mass-deployment guide (Intune/GPO), firewall rules and troubleshooting before the first pilot.

Instructions

  1. Write the deployment guide.
  2. Krishna Validate on a pilot client setup.

Done when

Guide used successfully by first pilot's IT team.

Inputs needed

Installer; tested switches.

Depends on

T-074

T-119Design QA & accessibility auditUI/UX Design TransformationW2Launch-critical KevinNot started15-Jan-27

Why now. The build must match design and be accessible before customers see it.

Instructions

  1. Compare build vs design; check WCAG contrast, focus order, text sizes; log issues.
  2. Kevin + Bharath Prioritise and fix.

Done when

No high-severity design or accessibility issues at release.

Inputs needed

Staging URL; Figma file.

Depends on

T-084

T-120UAT kits for pilot clientsQA & Testing TransformationW2Launch-critical KrishnaNot started15-Jan-27

Why now. Pilot clients sign off faster with a clear UAT script.

Instructions

  1. Write UAT scripts, sign-off sheets, feedback forms.
  2. Krishna Run sessions with clients.

Done when

UAT signed by first pilot.

Inputs needed

Test cases; pilot list.

Depends on

T-065

T-121Performance & load testsQA & Testing TransformationW2Launch-critical Dev vendorNot started15-Jan-27

Why now. Ingestion and report APIs must handle launch volumes.

Instructions

  1. Write k6/JMeter scripts and analyse results.
  2. Vendor Run against real infrastructure.

Done when

Target load passed with headroom.

Inputs needed

Staging infrastructure.

Depends on

T-058

T-122Product mockupsMarketing TransmissionW2Launch-critical KevinNot started15-Jan-27

Why now. Marketing needs product visuals with realistic data before live customers exist.

Instructions

  1. Build device mockups.
  2. Kevin Approve.

Done when

Mockup set for site, deck and social.

Inputs needed

Designs; demo data.

Depends on

T-075 T-080

Unlocks

T-123

T-123Brochures & sell sheetsMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. Sellers need leave-behinds per vertical.

Instructions

  1. Create the brochure and vertical one-pagers.
  2. Deepan Approve.

Done when

Four one-pagers ready.

Inputs needed

ICP; mockups.

Depends on

T-076 T-094 T-122

T-124Keyword & topic researchMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. Content should target what the launch segment actually searches and asks AI assistants.

Instructions

  1. Build topic clusters and intent map from web research.
  2. Deepan Prioritise.

Done when

Prioritised topic map.

Inputs needed

ICP.

Depends on

T-076

Unlocks

T-125 T-126 T-127

T-125Blog & thought leadershipMarketing TransmissionW2Launch-critical DeepanNot started31-Jan-27

Why now. Articles build search visibility and give sales something to share.

Instructions

  1. Write six launch articles (hybrid work, productivity, DPDP, burnout).
  2. Deepan Subject-matter review.

Done when

Six articles published by end of January.

Inputs needed

Topic map.

Depends on

T-124

Unlocks

T-174 T-176 T-177

T-126AEO / GEO optimisationMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. Buyers increasingly ask AI assistants for tool recommendations; content must be easy for them to quote.

Instructions

  1. Add FAQs, definitions and comparison sections structured for AI answers.
  2. Deepan Approve.

Done when

Key pages restructured for AEO/GEO.

Inputs needed

Copy; topic map.

Depends on

T-095 T-124

Unlocks

T-195

T-127Content calendarMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. A calendar turns launch messaging into a steady drumbeat.

Instructions

  1. Plan eight weeks across LinkedIn, X, Instagram, YouTube.
  2. Deepan Approve.

Done when

Approved 8-week calendar.

Inputs needed

ICP; topic map; launch date.

Depends on

T-076 T-124

Unlocks

T-128 T-129

T-128Social creatives & carouselsMarketing TransmissionW2Launch-critical KevinNot started15-Jan-27

Why now. Visual posts carry the calendar.

Instructions

  1. Produce creatives and carousels.
  2. Kevin Tweak and approve.

Done when

Creatives ready for first four weeks.

Inputs needed

Calendar; brand guidelines.

Depends on

T-094 T-127

Unlocks

T-130

T-129Post copy & hooksMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. Founder-led posts are the cheapest early reach.

Instructions

  1. Write posts and hooks; founder posts in Deepan's voice.
  2. Deepan Approve and personalise.

Done when

First four weeks of posts approved.

Inputs needed

Calendar.

Depends on

T-127

Unlocks

T-130

T-130Publishing & schedulingMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. Posting needs a person or approved browser posting.

Instructions

  1. Prepare ready-to-post packs; post via browser with approval if asked.
  2. Deepan Post or approve.

Done when

Posting on schedule from launch week.

Inputs needed

Approved posts.

Depends on

T-128 T-129

Unlocks

T-178 T-196

T-131Landing page buildMarketing TransmissionW2Launch-critical BharathIn progress10-Jan-27

Why now. The site must be live before outreach starts.

Instructions

  1. Build responsive pages, forms and analytics tags.
  2. Bharath Review and deploy.

Done when

Site live by 10 January.

Inputs needed

Designs; hosting.

Depends on

T-096

Unlocks

T-132 T-133 T-135 T-197

T-132Technical SEO auditMarketing TransmissionW2Launch-critical BharathNot started15-Jan-27

Why now. A technical audit before launch avoids indexing and speed problems.

Instructions

  1. Audit meta tags, headings, speed, links, indexation.
  2. Bharath Fix.

Done when

No critical SEO issues.

Inputs needed

Live site.

Depends on

T-131

T-133Schema markupMarketing TransmissionW2Launch-critical BharathNot started15-Jan-27

Why now. Structured data helps search engines and AI answers describe Teemly correctly.

Instructions

  1. Write JSON-LD for Organization, SoftwareApplication, Product, FAQ, Article.
  2. Bharath Deploy.

Done when

Schema validates on all key pages.

Inputs needed

Live pages.

Depends on

T-131

T-134Scripts & storyboardsMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. A short explainer is the fastest way to show the product at launch.

Instructions

  1. Write explainer and demo scripts with shot lists.
  2. Deepan Approve.

Done when

Scripts approved.

Inputs needed

Positioning; demo flow.

Depends on

T-041

Unlocks

T-156 T-182

T-135Press releases & media pitchesMarketing TransmissionW2Launch-critical DeepanNot started15-Jan-27

Why now. A launch announcement creates a moment for outreach and press.

Instructions

  1. Draft press release and media pitches.
  2. Deepan Approve and send.

Done when

Launch release issued.

Inputs needed

Launch date; quotes.

Depends on

T-131

T-136Lead list researchSales & Business Development TransmissionW2Launch-critical NaveenNot started15-Jan-27

Why now. Outbound needs a list of real accounts and decision makers in the launch segment.

Instructions

  1. Research target accounts and decision makers from public sources into a sheet.
  2. Naveen Verify contacts; enrich with paid tools if available.

Done when

200+ verified accounts in the launch segment.

Inputs needed

ICP; any paid data tools.

Depends on

T-076

Unlocks

T-138 T-159 T-183

T-137Security questionnairesSecurity, Privacy & Compliance ConversionW2Launch-critical KrishnaNot started15-Jan-27

Why now. Larger prospects send security questionnaires before buying.

Instructions

  1. Build an answer bank and answer incoming questionnaires.
  2. Krishna Confirm every answer is true.

Done when

Answer bank covers common questionnaires.

Inputs needed

Threat model; policies.

Depends on

T-070

Unlocks

T-184

T-138Account research briefsSales & Business Development ConversionW2Launch-critical NaveenNot started15-Jan-27

Why now. Prepared sellers convert more.

Instructions

  1. Write pre-call briefs.
  2. Naveen Read before the call.

Done when

Brief for every first call.

Inputs needed

Meeting list.

Depends on

T-136

T-139ROI calculatorsSales & Business Development ConversionW2Launch-critical NaveenNot started15-Jan-27

Why now. Buyers approve spend when the ROI is concrete for their vertical.

Instructions

  1. Build ROI calculators for IT services, BPO, agency and accounting.
  2. Naveen Validate assumptions.

Done when

Four calculators ready.

Inputs needed

Locked pricing; vertical assumptions.

Depends on

T-076 T-077

T-140Objection handling guideSales & Business Development ConversionW2Launch-critical NaveenNot started15-Jan-27

Why now. Privacy, price, employee trust and IT approval are the predictable objections; answers must match the privacy texts exactly.

Instructions

  1. Update the guide with launch facts and approved privacy wording.
  2. Naveen Refine from real calls.

Done when

Guide updated and used on calls.

Inputs needed

Earlier objection guide; privacy texts.

Depends on

T-078

Unlocks

T-141

T-141Email & LinkedIn sequencesSales & Business Development TransmissionW2Launch-critical NaveenNot started15-Jan-27

Why now. Multi-step email and LinkedIn sequences turn the list into conversations.

Instructions

  1. Write 4-6 step sequences per persona in the launch segment.
  2. Naveen Approve.

Done when

Approved sequences ready to send at launch.

Inputs needed

ICP; objection guide.

Depends on

T-076 T-140

Unlocks

T-159

T-142Discount & approval matrixSales & Business Development ConversionW2Launch-critical DeepanNot started15-Jan-27

Why now. Guardrails stop discounting from eroding price before it is proven.

Instructions

  1. Draft discount bands and approvals.
  2. Deepan Set policy.

Done when

Matrix published.

Inputs needed

Locked pricing.

Depends on

T-077

T-143Release notes & changelogProduct Management RetentionW2Launch-critical KrishnaNot started15-Jan-27

Why now. Customers adopt what they understand. Clear release notes reduce support load from day one.

Instructions

  1. Write customer-facing and internal notes.
  2. Krishna Review.

Done when

Notes published with every release.

Inputs needed

Merged changes per release.

Depends on

T-111

T-144Monitoring & alertingDevOps, Cloud & IT RetentionW2Launch-critical Pune infra vendorNot started15-Jan-27

Why now. Customers lose trust fast if outages go unnoticed.

Instructions

  1. Configure logging, metrics, uptime checks and alert rules.
  2. Vendor Wire alerts to on-call.

Done when

Alerts fire in a staged outage test.

Inputs needed

Environments.

Depends on

T-052

Unlocks

T-146

T-145Backup & disaster recoveryDevOps, Cloud & IT RetentionW2Launch-critical Pune infra vendorNot started15-Jan-27

Why now. Customer data must be recoverable; enterprise buyers will ask.

Instructions

  1. Write backup policy, RPO/RTO targets and restore runbooks.
  2. Vendor Run a restore drill.

Done when

Successful restore drill recorded.

Inputs needed

Environments; retention policy.

Depends on

T-052

T-146Production deploys & incidentsDevOps, Cloud & IT RetentionW2Launch-critical KrishnaNot started15-Jan-27

Why now. Production changes and incidents need a rehearsed procedure and a person on call.

Instructions

  1. Write deploy runbook, rollback steps, incident template and post-incident report format.
  2. Team Hold credentials, execute, be on call.

Done when

First production release follows the runbook.

Inputs needed

Pipelines; monitoring.

Depends on

T-063 T-144

T-147Data-rights request processSecurity, Privacy & Compliance RetentionW2Launch-critical KrishnaNot started15-Jan-27

Why now. Access and erasure requests must be answerable within the law's timelines.

Instructions

  1. Write workflow and templates.
  2. Krishna Operate.

Done when

Process tested end to end.

Inputs needed

DPDP assessment.

Depends on

T-035

T-148Onboarding playbookCustomer Success & Support RetentionW2Launch-critical CS lead (to hire)Not started15-Jan-27

Why now. Time-to-value decides whether pilots convert. A day-0 to day-30 plan makes it repeatable.

Instructions

  1. Write onboarding playbook, checklists and success milestones.
  2. CS lead Run onboarding.

Done when

Playbook used for every pilot.

Inputs needed

Specs; deployment guide.

Depends on

T-022

Unlocks

T-175 T-207

T-149Employee communication kitCustomer Success & Support RetentionW2Launch-critical KrishnaNot started15-Jan-27

Why now. Employees accept Teemly when it is announced transparently. This kit protects trust and supports consent.

Instructions

  1. Draft announcement, FAQ and consent explainer for client staff.
  2. Client HR Approve and send.

Done when

Kit used by first pilot.

Inputs needed

Approved privacy texts.

Depends on

T-078

T-150Training materialsCustomer Success & Support RetentionW2Launch-critical CS lead (to hire)Not started15-Jan-27

Why now. Admins and managers need to read reports correctly to get value.

Instructions

  1. Training decks, quick-reference cards and video scripts.
  2. CS lead Deliver training.

Done when

Training delivered to first pilot.

Inputs needed

Built reports.

Depends on

T-086

T-151Help centre articlesCustomer Success & Support RetentionW2Launch-critical CS lead (to hire)Not started15-Jan-27

Why now. Self-serve answers cut support load from day one.

Instructions

  1. Write how-to, troubleshooting and FAQ articles for every module.
  2. CS lead Review and publish.

Done when

Help centre covers every Phase 1 module.

Inputs needed

Built product.

Depends on

T-085

Unlocks

T-152 T-212

T-152Support macros & templatesCustomer Success & Support RetentionW2Launch-critical CS lead (to hire)Not started15-Jan-27

Why now. Consistent replies and SLAs build trust.

Instructions

  1. Canned replies, escalation templates, SLA wording.
  2. CS lead Use and refine.

Done when

Macros in use.

Inputs needed

Help articles.

Depends on

T-151

Unlocks

T-186

T-153Competitor intelligenceFounder's Office & Strategy FeedbackW2Launch-critical DeepanNot started15-Jan-27

Why now. Positioning, battlecards and the website all need a current view of ActivTrak, Hubstaff, Teramind and others. A v1 was verified for the investor deck; it needs a launch-time refresh and then a monthly watch.

Instructions

  1. Refresh the feature and pricing matrix from live sources, with links and dates.
  2. Set up a monthly scheduled task that flags price changes, launches and notable reviews.
  3. Deepan Add field notes from sales calls each month.

Done when

Dated matrix with sources, and a monthly scheduled watch running.

Inputs needed

Earlier verified competitor data; any competitor names prospects mention.

Depends on

None. Can start now.

Unlocks

T-154

T-154Competitive battlecardsSales & Business Development ConversionW2Launch-critical NaveenNot started15-Jan-27

Why now. Prospects will compare Teemly to ActivTrak, Hubstaff and Teramind.

Instructions

  1. Write battlecards with positioning, landmines and proof points.
  2. Naveen Field-validate.

Done when

Three battlecards in use.

Inputs needed

Competitor matrix.

Depends on

T-153

T-155AI-generated imageryUI/UX Design TransmissionW2Strengthen KevinNot started15-Jan-27

Why now. Imagery for marketing and empty states, generated inside Figma (uses Figma AI credits).

Instructions

  1. Generate options in Figma.
  2. Kevin Select and approve; check usage rights.

Done when

Approved images placed.

Inputs needed

Brand guidelines; image briefs.

Depends on

T-094

T-156Motion graphicsMarketing TransmissionW2Strengthen KevinNot started15-Jan-27

Why now. Motion makes the explainer clearer.

Instructions

  1. Build animated sequences in Figma; export MP4.
  2. Kevin Polish timing; add music and voice-over.

Done when

Explainer video published.

Inputs needed

Scripts; designs.

Depends on

T-134

T-157Media & event researchMarketing TransmissionW2Strengthen DeepanNot started15-Jan-27

Why now. The right events and journalists multiply founder effort.

Instructions

  1. Research journalists, publications, HR-tech events.
  2. Deepan Build relationships.

Done when

Shortlist of 10 events and 20 journalists.

Inputs needed

ICP.

Depends on

T-076

T-158Discovery calls, demos, closingSales & Business Development ConversionW3Mandatory NaveenNot started31-Mar-27

Why now. This is where the plan's outcome happens: converting pipeline prospects into paid pilots after launch.

Instructions

  1. Prep and debrief every call.
  2. Naveen + Deepan Run discovery, demos and closing.

Done when

First paid pilots signed.

Inputs needed

Deck; demo tenant; proposal; contract; DPA.

Depends on

T-112 T-113 T-115 T-116 T-117

Unlocks

T-161

T-159Sending & follow-upsSales & Business Development TransmissionW3Launch-critical NaveenNot started31-Mar-27

Why now. Sending and following up is where outbound succeeds or fails. No email or CRM is connected yet, so this stays mostly human.

Instructions

  1. Prepare send-ready drafts and follow-up queues.
  2. Naveen Send and manage replies.

Done when

Sequences running for the full launch list.

Inputs needed

Sequences; list.

Depends on

T-136 T-141

T-160Contract first-pass reviewSales & Business Development ConversionW3Launch-critical NaveenNot started31-Mar-27

Why now. Customer redlines need a fast first pass.

Instructions

  1. Flag risky clauses and suggest redlines.
  2. Counsel Sign off.

Done when

Redlines turned in under 3 days.

Inputs needed

Customer's contract changes.

Depends on

T-116

T-161Pipeline reportingSales & Business Development FeedbackW3Launch-critical NaveenNot started31-Mar-27

Why now. Pipeline and win/loss data show which objections and segments to fix.

Instructions

  1. Weekly pipeline and win/loss report.
  2. Naveen Keep records updated.

Done when

Weekly report running.

Inputs needed

Pipeline export.

Depends on

T-158

T-162Advisor & board packsFounder's Office & Strategy InputW3Strengthen DeepanNot started31-Mar-27

Why now. Once investors are in, a short quarterly pack keeps trust high and makes the next round easier.

Instructions

  1. Draft a 10-slide pack from the dashboard and MIS.
  2. Deepan Own the narrative and final numbers.

Done when

Pack sent each quarter.

Inputs needed

KPIs, milestones, risks, asks.

Depends on

T-100

T-163Pitch deck build & updatesFundraising & Investor Relations InputW3Strengthen DeepanNot started31-Mar-27

Why now. The 21-slide investor deck exists. Refresh it once launch data exists, for the long-term investors Senthil is bringing.

Instructions

  1. Update traction, pricing and use-of-funds slides; keep Teemly branding.
  2. Deepan Approve every number.

Done when

Refreshed deck approved.

Inputs needed

Launch metrics; locked pricing; pipeline status (described only as pipeline, no seat counts or closing dates).

Depends on

T-005

Unlocks

T-164 T-165 T-203

T-164Teaser & executive summaryFundraising & Investor Relations InputW3Strengthen DeepanNot started31-Mar-27

Why now. A one-page teaser opens doors without sending the full deck.

Instructions

  1. Write a one-page teaser and a two-page summary.
  2. Deepan Final read.

Done when

Teaser and summary ready as PDF.

Inputs needed

Refreshed deck.

Depends on

T-163

Unlocks

T-204

T-165Investor Q&A and objection prepFundraising & Investor Relations InputW3Strengthen DeepanNot started31-Mar-27

Why now. The Q&A and objection guide exists. Update it with launch evidence so answers rely on data, not projections.

Instructions

  1. Update answers and add new questions from recent meetings.
  2. Deepan Rehearse.

Done when

Updated guide rehearsed.

Inputs needed

Launch metrics; new investor questions.

Depends on

T-163

Unlocks

T-205

T-166Investor proposal variantsFundraising & Investor Relations InputW3Strengthen DeepanNot started31-Mar-27

Why now. Senthil's investors want two proposal types: debt-based, and long-term equity plus asset holding. Both need clear terms side by side.

Instructions

  1. Draft both proposals with term comparison and impact on cap table and cash.
  2. Sathya + counsel Structure and review.
  3. Deepan Negotiate.

Done when

Two reviewed proposals ready to share.

Inputs needed

Investor preferences; model; cap table.

Depends on

T-005 T-009

T-167ESOP policyLegal & Company Secretarial InputW3Strengthen DeepanNot started31-Mar-27

Why now. An ESOP pool helps attract senior engineers once the team grows.

Instructions

  1. Draft ESOP plan and grant letters.
  2. Counsel + Sathya Finalise.

Done when

ESOP plan adopted.

Inputs needed

Cap table.

Depends on

T-009

T-168HR policies & handbookPeople & Talent (HR) InputW3Strengthen DeepanNot started31-Mar-27

Why now. Policies matter more as the team grows.

Instructions

  1. Draft leave, remote, conduct, IT use and POSH policies.
  2. Counsel Check; adopt.

Done when

Handbook adopted.

Inputs needed

Founder preferences.

Depends on

None. Can start now.

T-169Performance frameworkPeople & Talent (HR) InputW3Strengthen DeepanNot started31-Mar-27

Why now. Clear goals and reviews keep people aligned to the OKRs.

Instructions

  1. Goal templates, review forms, career ladders.
  2. Deepan Run reviews.

Done when

First review cycle completed.

Inputs needed

OKRs.

Depends on

T-001

T-170Code to FigmaUI/UX Design TransformationW3Strengthen KevinNot started31-Mar-27

Why now. Pushing built pages back into Figma keeps the design file truthful after launch changes.

Instructions

  1. Push pages into Figma for side-by-side review.
  2. Kevin Review differences.

Done when

Design file reflects production.

Inputs needed

Built pages.

Depends on

T-084

T-171Anomaly & burnout signalsData, Analytics & AI TransformationW3Strengthen KrishnaNot started31-Mar-27

Why now. Burnout and anomaly signals need real baseline data. Building them before launch would mean guessing.

Instructions

  1. Build baselines and team/org-level alert logic.
  2. Krishna Validate on real data; ethics review.

Done when

Signals validated on pilot data.

Inputs needed

6-8 weeks of real usage data.

Depends on

T-069

T-172Penetration testingSecurity, Privacy & Compliance TransformationW3Strengthen KrishnaNot started31-Mar-27

Why now. An external pen test is expected by enterprise buyers.

Instructions

  1. Write scope and RFP; track remediation.
  2. External firm Perform the test.

Done when

Report received; criticals fixed.

Inputs needed

Budget; vendor shortlist.

Depends on

T-111

T-173Event & print collateralMarketing TransmissionW3Strengthen KevinNot started31-Mar-27

Why now. Print collateral is needed only when events are booked.

Instructions

  1. Design standees and booth panels.
  2. Kevin Final proof; printing.

Done when

Collateral printed for first event.

Inputs needed

Event details.

Depends on

T-094

T-174Whitepapers & e-booksMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Gated long-form content captures leads once there is traffic.

Instructions

  1. Write whitepapers or e-books.
  2. Deepan Approve claims.

Done when

First gated asset live.

Inputs needed

Topic map; data.

Depends on

T-125

T-175Case studiesMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Proof from real pilots converts better than any claim.

Instructions

  1. Draft case study.
  2. Deepan Interview client; get approval.

Done when

First case study approved by client.

Inputs needed

Pilot results; client interview.

Depends on

T-148

Unlocks

T-214

T-176NewsletterMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. A newsletter keeps prospects warm between conversations.

Instructions

  1. Draft monthly on a schedule.
  2. Deepan Approve and send.

Done when

Newsletter sent monthly.

Inputs needed

Published content.

Depends on

T-125

T-177Webinar contentMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Webinars convert interest into demos.

Instructions

  1. Deck, script, promo and follow-up emails.
  2. Deepan Present live.

Done when

First webinar held.

Inputs needed

Topic; speakers.

Depends on

T-125

T-178Community engagementMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Replies build relationships; they need a person.

Instructions

  1. Draft replies.
  2. Deepan Engage personally.

Done when

Replies within 24 hours.

Inputs needed

Comments and DMs.

Depends on

T-130

T-179Ad copy & creative variantsMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Paid ads only make sense once the site converts and messaging is proven.

Instructions

  1. Write Google, LinkedIn, Meta ad variants.
  2. Deepan Approve.

Done when

Ad variants approved.

Inputs needed

Proven messaging.

Depends on

T-076 T-094

Unlocks

T-181

T-180Campaign planMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. A plan keeps spend tied to measurable outcomes.

Instructions

  1. Structure, audiences, budget and tracking plan.
  2. Deepan Set budget.

Done when

Approved campaign plan.

Inputs needed

Budget; ICP.

Depends on

T-007 T-076

Unlocks

T-181

T-181Campaign launch & spendMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Ad accounts and payments need a person.

Instructions

  1. Setup checklist.
  2. Deepan Launch and manage spend.

Done when

Campaign live.

Inputs needed

Plan; creatives.

Depends on

T-179 T-180

Unlocks

T-198

T-182Filming, voice-over, editingMarketing TransmissionW3Strengthen DeepanNot started31-Mar-27

Why now. Live video needs filming and editing.

Instructions

  1. Shot list and edit notes.
  2. Team Film, record, edit.

Done when

Video published.

Inputs needed

Script.

Depends on

T-134

T-183Personalised openers at scaleSales & Business Development TransmissionW3Strengthen NaveenNot started31-Mar-27

Why now. Personalised first lines lift reply rates once volume grows.

Instructions

  1. Write account-specific openers from research.
  2. Naveen Spot-check.

Done when

Openers added for each batch.

Inputs needed

Account list.

Depends on

T-136

T-184RFP & tender responsesSales & Business Development ConversionW3Strengthen DeepanNot started31-Mar-27

Why now. Government and public-sector tenders are a separate track once the product and compliance pack exist.

Instructions

  1. Draft responses and compliance matrices.
  2. Deepan Eligibility documents; signatures.

Done when

First tender submitted.

Inputs needed

Tender documents.

Depends on

T-137

T-185ISO 27001 policy setSecurity, Privacy & Compliance RetentionW3Strengthen KrishnaIn progress31-Mar-27

Why now. ISO 27001 is in progress per earlier materials; policies come first, certification later.

Instructions

  1. Draft ISMS scope, risk method and core policies.
  2. Team Implement controls; engage auditor.

Done when

Policy set adopted.

Inputs needed

Scope decision.

Depends on

T-035

Unlocks

T-209 T-210

T-186Ticket triage & reply draftsCustomer Success & Support RetentionW3Strengthen CS lead (to hire)Not started31-Mar-27

Why now. Triage keeps response times low as pilots grow.

Instructions

  1. Categorise and draft replies (live use needs a helpdesk connection).
  2. CS lead Send; handle escalations.

Done when

First response within SLA.

Inputs needed

Ticket inbox.

Depends on

T-152

Unlocks

T-199

T-187Customer health scoreCustomer Success & Support RetentionW3Strengthen CS lead (to hire)Not started31-Mar-27

Why now. A health score flags at-risk pilots before they churn.

Instructions

  1. Build the model and dashboard.
  2. CS lead Act on red accounts.

Done when

Health score reviewed weekly.

Inputs needed

Usage and support data.

Depends on

T-068

Unlocks

T-188

T-188Business reviews (QBRs)Customer Success & Support RetentionW3Strengthen CS lead (to hire)Not started31-Mar-27

Why now. Showing each client their own insights and ROI makes Teemly hard to remove.

Instructions

  1. Build client-ready review decks.
  2. CS lead Present.

Done when

QBR held with each pilot.

Inputs needed

Client data; health score.

Depends on

T-187

Unlocks

T-211

T-189Code Connect mappingUI/UX Design LeverageW3Strengthen BharathNot started31-Mar-27

Why now. Linking Figma components to code means future screens come with real code snippets.

Instructions

  1. Map components with Code Connect.
  2. Bharath Maintain as code changes.

Done when

Core components mapped.

Inputs needed

Component library; repository.

Depends on

T-079 T-084

T-190IntegrationsEngineering LeverageW3Strengthen Dev vendorNot started31-Mar-27

Why now. SSO and HRMS integrations deepen adoption and switching cost, but are not needed for the first pilots.

Instructions

  1. Build connectors for Google/Microsoft SSO, then HRMS and Slack/Teams.
  2. Vendor Test with partner sandboxes.

Done when

SSO live; next integration chosen by customer demand.

Inputs needed

Partner credentials; customer demand.

Depends on

T-057

T-191Teemly AI assistantData, Analytics & AI LeverageW3Strengthen KrishnaNot started31-Mar-27

Why now. The AI assistant multiplies the value of the reports, but only once the reports are reliable. AI-native is a roadmap claim, not a launch claim.

Instructions

  1. Design prompts, retrieval over org-level data, guardrails and answer formats.
  2. Krishna + Deepan Product and privacy approval.

Done when

Assistant answers a defined question set accurately.

Inputs needed

Stable report data; privacy rules.

Depends on

T-035 T-068

Unlocks

T-193

T-192SOPs & process docsDelivery, Operations & Vendor Management LeverageW3Strengthen PrinishaNot started31-Mar-27

Why now. Written SOPs make releases, onboarding and support repeatable as the team grows.

Instructions

  1. Write SOPs.
  2. Team Adopt.

Done when

SOPs for release, onboarding, support.

Inputs needed

Current practice.

Depends on

None. Can start now.

T-193AI evaluationData, Analytics & AI FeedbackW3Strengthen KrishnaNot started31-Mar-27

Why now. Without evals, AI quality silently drifts.

Instructions

  1. Build test sets, rubrics and regression evals.
  2. Krishna Review failure cases.

Done when

Evals run on every AI change.

Inputs needed

Question set; expected answers.

Depends on

T-191

T-194Ad-hoc analysisData, Analytics & AI FeedbackW3Strengthen DeepanNot started31-Mar-27

Why now. Specific questions answered from data beat opinions.

Instructions

  1. Analyse and chart.
  2. Deepan Act on it.

Done when

Answer delivered with method.

Inputs needed

A question and a data export.

Depends on

None. Can start now.

T-195AI search visibility trackingMarketing FeedbackW3Strengthen DeepanNot started31-Mar-27

Why now. Shows whether AI assistants and search describe Teemly correctly, and where competitors are cited instead.

Instructions

  1. Run a monthly scheduled check of answers to 20 target questions; report changes.
  2. Deepan Act on findings.

Done when

Monthly visibility report running.

Inputs needed

Target questions buyers ask.

Depends on

T-126

T-196Social analyticsMarketing FeedbackW3Strengthen DeepanNot started31-Mar-27

Why now. Social data shows which messages reach the ICP.

Instructions

  1. Monthly report with what to do more and less of.
  2. Deepan Export data.

Done when

Monthly report used to adjust the calendar.

Inputs needed

Platform exports.

Depends on

T-130

T-197A/B test variantsMarketing FeedbackW3Strengthen DeepanNot started31-Mar-27

Why now. Experiments replace opinion on headline and CTA once traffic exists.

Instructions

  1. Write variants and a test plan.
  2. Deepan Run test; decide.

Done when

First test concluded with a decision.

Inputs needed

Traffic; conversion goal.

Depends on

T-131

T-198Performance analysisMarketing FeedbackW3Strengthen DeepanNot started31-Mar-27

Why now. Spend should move toward what converts.

Instructions

  1. Weekly analysis and recommendations.
  2. Deepan Decide changes.

Done when

Weekly decisions logged.

Inputs needed

Ad exports.

Depends on

T-181

T-199Feedback & churn analysisCustomer Success & Support FeedbackW3Strengthen KrishnaNot started31-Mar-27

Why now. Feedback and churn reasons feed the roadmap.

Instructions

  1. Theme analysis with recommended fixes.
  2. Krishna Prioritise fixes.

Done when

Monthly insight feeds the roadmap.

Inputs needed

NPS, tickets, churn notes.

Depends on

T-186

T-200SaaS metricsFinance & Accounts FeedbackW3Strengthen DeepanNot started31-Mar-27

Why now. MRR, churn, NRR, CAC and LTV are what Series A investors will judge.

Instructions

  1. Calculate metrics and build the dashboard.
  2. Deepan Supply billing data.

Done when

Metrics reported monthly.

Inputs needed

Billing data.

Depends on

T-114

Unlocks

T-201

T-201Internal dashboardsData, Analytics & AI FeedbackW3Strengthen KrishnaNot started31-Mar-27

Why now. Usage, conversion and support dashboards show where the loop is leaking.

Instructions

  1. Build internal dashboards.
  2. Team Supply exports.

Done when

Dashboards refreshed weekly.

Inputs needed

Data exports.

Depends on

T-200

T-202Market sizing (TAM / SAM / SOM)Founder's Office & Strategy InputW4Later DeepanNot started30-Jun-27

Why now. Market sizing already exists in the investor deck. It only needs a refresh when Series A preparation starts, using real conversion data.

Instructions

  1. Rebuild bottom-up sizing using real ARPU and segment conversion; cite every source.
  2. Deepan Approve method and figures.

Done when

Refreshed TAM/SAM/SOM with sources, labelled estimates.

Inputs needed

Actual customer and pricing data from the first two quarters.

Depends on

T-003

T-203Investor research & target listFundraising & Investor Relations InputW4Later DeepanNot started30-Jun-27

Why now. Series A follows traction. Build the investor list once there are real metrics to show.

Instructions

  1. Research investors by thesis, stage, cheque size and portfolio fit, with warm-path notes.
  2. Deepan Prioritise and find warm intros.

Done when

Prioritised list of 30-50 investors.

Inputs needed

Target round size and timing.

Depends on

T-163

Unlocks

T-204

T-204Outreach & follow-up draftsFundraising & Investor Relations InputW4Later DeepanNot started30-Jun-27

Why now. Personalised outreach converts warm intros into meetings.

Instructions

  1. Draft personalised intro and follow-up emails.
  2. Deepan Send from own email.

Done when

Outreach sent to all priority investors.

Inputs needed

Prioritised list; teaser.

Depends on

T-164 T-203

Unlocks

T-205

T-205Pitch meetings & negotiationFundraising & Investor Relations InputW4Later DeepanNot started30-Jun-27

Why now. Pitching and negotiation are founder-led; good preparation makes each meeting sharper.

Instructions

  1. Brief before, debrief after each meeting.
  2. Deepan Pitch, negotiate, close.

Done when

Round closed.

Inputs needed

Meeting schedule.

Depends on

T-165 T-204

T-206Legal opinions & disputesLegal & Company Secretarial InputW4Later Legal counselNot started30-Jun-27

Why now. Legal opinions and disputes are human work.

Instructions

  1. Background research.
  2. Counsel Advise.

Done when

Matter resolved.

Inputs needed

Matter details.

Depends on

None. Can start now.

T-207Partner programme designSales & Business Development TransmissionW4Later DeepanNot started30-Jun-27

Why now. Channel partners (HR consultants, IT resellers, Zoho partners) are the Year 2 route to reach without 10x founder effort, once onboarding is repeatable.

Instructions

  1. Design tiers, margins and rules.
  2. Deepan Decide commercials.

Done when

Partner programme published.

Inputs needed

Repeatable onboarding; margin model.

Depends on

T-148

Unlocks

T-208

T-208Partner enablement kitSales & Business Development TransmissionW4Later DeepanNot started30-Jun-27

Why now. Partners sell only what they understand.

Instructions

  1. Build partner deck, training guide and co-branded collateral.
  2. Deepan Train partners.

Done when

Kit used by first partner.

Inputs needed

Partner programme.

Depends on

T-207

T-209SOC 2 readinessSecurity, Privacy & Compliance RetentionW4Later KrishnaNot started30-Jun-27

Why now. SOC 2 matters when US enterprise buyers ask for it.

Instructions

  1. Map controls and gaps.
  2. Team Implement; auditor.

Done when

Readiness gap list closed.

Inputs needed

Demand signal.

Depends on

T-185

T-210Audit evidence collectionSecurity, Privacy & Compliance RetentionW4Later KrishnaNot started30-Jun-27

Why now. Audits need evidence collected continuously, not at the last minute.

Instructions

  1. Build evidence checklist and folders.
  2. Team Collect evidence from systems.

Done when

Evidence ready for audit.

Inputs needed

Control list.

Depends on

T-185

T-211Renewals & upsellCustomer Success & Support RetentionW4Later DeepanNot started30-Jun-27

Why now. Renewals and upsells follow proven value.

Instructions

  1. Renewal reminders and proposal drafts.
  2. Deepan Negotiate.

Done when

First renewal closed.

Inputs needed

QBR outcomes.

Depends on

T-188

T-212In-app help assistant knowledge baseCustomer Success & Support LeverageW4Later KrishnaNot started30-Jun-27

Why now. An in-app help assistant scales support without headcount, once the help centre is mature.

Instructions

  1. Structure knowledge base and guardrails.
  2. Krishna Approve answers.

Done when

Assistant resolves common questions.

Inputs needed

Help centre.

Depends on

T-151

T-213Benchmark reportsData, Analytics & AI CompoundingW4Later DeepanNot started30-Jun-27

Why now. Anonymised benchmarks become an asset that grows with every customer, subject to consent and contracts.

Instructions

  1. Produce benchmark reports.
  2. Deepan Data-governance approval.

Done when

First benchmark report published.

Inputs needed

Sufficient anonymised data; legal clearance.

Depends on

T-068 T-078

T-214Award & speaker applicationsMarketing CompoundingW4Later DeepanNot started30-Jun-27

Why now. Awards and talks compound brand trust once there are results to show.

Instructions

  1. Draft applications and abstracts.
  2. Deepan Submit; speak.

Done when

First award or talk submitted.

Inputs needed

Case studies.

Depends on

T-175

Full task cards are also in the Execution Playbook ↗, and live status is in the Task Delivery Tracker ↗.

Trust & compliance

Compliance roadmap, with honest status

Trust is designed into the product from the specification stage. Certifications are on the roadmap with target windows, not claimed as complete. Each track links to the tasks that deliver it.

TrackWhat it coversStatusEvidence or targetTasks
Privacy by designOrg-level insights first, employee consent, employee-controlled screenshot blur, role-based accessIn progressRole-Based Access Matrix ↗T-036 T-060
DPDP Act 2023Gap assessment, consent texts, DPA and a data-rights request processIn progressPrivacy & DPDP phase, EXE Agent Build Playbook ↗T-035 T-078 T-117 T-147
India data residencyPrimary cloud in AWS Mumbai (ap-south-1)PlannedInfrastructure, Security & Compliance Guide ↗T-032
Signed Windows agentCode-signing certificate, Microsoft Partner Center verification, Microsoft Store listingPlannedPackaging, signing & trust phase, EXE Agent Build Playbook ↗T-073
Secure engineeringSTRIDE threat model, security review on every pull request, release go/no-goPlannedSecurity hardening phase, EXE Agent Build Playbook ↗T-070 T-071 T-111
Independent penetration testExternal firm tests the agent, ingestion and portalsPlannedQ1 2027, after launchT-172
ISO 27001Policy set first, then controls and certification auditIn progressPolicies Q1 2027 · certification laterT-185
SOC 2Control mapping and readiness for US enterprise buyersPlanned2027, driven by US demandT-209 T-210

Legal texts (privacy notice, consent, DPA) are drafted for review and signed off by counsel before use.

Governance

How progress is reported and controlled

A fixed reporting rhythm and contract controls, set up alongside the build.

  • Weekly status report

    Progress, risks and decisions from every owner, compiled every Friday.

    T-042
    Starts W0
  • Risk & dependency register

    Owned risks with triggers and mitigations, reviewed weekly.

    T-004 T-026
    Starts W0
  • Milestone-based vendor contracts

    Statements of work with acceptance criteria and IP assignment; payment only on accepted milestones.

    T-013 T-027
    Starts W0
  • Independent code audits

    Each vendor milestone reviewed against the spec before acceptance.

    T-062 T-072
    Starts W1
  • Monthly investor update

    Highlights, KPIs, lowlights and asks on a fixed monthly date.

    T-101
    Starts W1
  • Quarterly advisor pack

    KPIs, risks and asks with a full appendix.

    T-162
    Starts W3