Live audit report
Workmap · 20/20

Kite Systems

B2B SaaS, developer observability tools

ENעב

Get your team interviewed

Forward this link to your employees. Each interview takes about 15 minutes on their phone, no prep needed. The report below updates as interviews come in.

What you could not have seen

The single heaviest thing on each person's month, from their own account of it. Ranked by hours, not by how loudly anyone complained.

  1. Feature ticket development (e.g., filters panel)
    100 h a month, 94% of everything Gil Baram mapped
  2. Repeat ticket handling in Intercom
    55 h a month, 85% of everything Yuval Stern mapped
  3. Bug fix and PR workflow
    36 h a month, 77% of everything Maya Oren mapped
  4. Post-build regression testing and bug ticketing
    19 h a month, 83% of everything Lior Dagan mapped
  5. Follow-up Email Sequence & Lead Handoff to Eran
    18 h a month, 49% of everything Noa Friedman mapped
People interviewed0
Automatable hours per month0includes 133.1 hrs/mo ad-hoc at 50%
Days back per month0623 h per month, counted in 8 hour days
Capacity this frees0.00.0 of one full time person

Automatable hours by employee

top 8 of 20 · hrs / month
Gil Baram113
Yuval Stern69.9
Maya Oren52.1
Noa Friedman42.4
Dana Katz35.5
Alon Peled28.7
Lior Dagan28.4
Michal Sela27.7

Feasibility split

High feasibility7
Medium feasibility35
Low feasibility7

12-month cumulative hours

top 3 candidates
2k0M1M121,919 h

Assumes phased delivery: candidate 1 live in month 2, candidates 2 and 3 by month 4.

Work that crosses people

3 chains mapped · 7 handoffs
Chain 1

Lead to onboarding handoff chain

4 people · 3 handoffs
Step 1 · SDRNoa FriedmanResearches and qualifies the lead, then writes a handoff note in Notion and pings Eran on Slack once it qualifies.
wait Eran typically picks up the handoff same day, sometimes next morning (up to 24 hours)
Step 2 · Head of SalesEran GoldPicks up the qualified lead, sends the proposal, and chases the contract to signature.
wait Slack ping sits a few hours before Dana books the kickoff call
Step 3 · Customer Success ManagerDana KatzBooks and holds the kickoff call, then asks DevOps to provision the tenant.
wait DevOps provisioning takes about 1 day, sometimes slipping to 2-3 days if Adi is busy
Step 4 · DevOps EngineerAdi RosenProvisions the tenant and confirms back in Slack when it is live.
Worst-case wait distribution100 h total
Chain 2

Release notes rewrite and distribution chain

3 people · 2 handoffs
Step 1 · Backend EngineerOmer BarSends raw release notes via Slack after each release.
wait Omer reviews within the same day (1-2 hours)
Step 2 · Product ManagerNir FeldRewrites the raw notes into customer-facing copy and shares them for Omer's sanity check.
wait Shir sends within 1-2 days
Step 3 · Marketing ManagerShir AdlerSends the approved notes out as an email blast and in-app banner.
Worst-case wait distribution50 h total
Chain 3

Demo booking and prep chain

3 people · 2 handoffs
Step 1 · SDRNoa FriedmanBooks the demo on Ben's calendar.
wait Demo booked 3-4 days in advance
Step 2 · Frontend EngineerGil BaramPreps the demo deck and environment before the call.
wait Gil preps the environment the day before or morning of the call
Step 3 · Account ExecutiveBen TzurRuns the live demo call and logs notes into HubSpot afterward.
Worst-case wait distribution120 h total

What to automate first

ranked by hours per month
High · 7Off-the-shelf connectors exist for every tool in the chain. Shippable in weeks.
Automate first
Medium · 35Needs custom integration, scripting or scraping. Real work, still bounded.
Low · 7The core work needs human judgment. Only the admin around it can automate.
Automate first28 h /mo2 processes · 27.5 h/mo · high feasibility, highest value.
Ranked by feasibility tier first, then monthly value. Bar length shows monthly value. The dashed frame holds the pilot shortlist: the high-feasibility processes worth at least half the best one.

Where the time leaks

Alon PeledCEO7
Michal SelaVP R&D18
Omer BarBackend Engineer13.4
Roni AlterBackend Engineer13
Gil BaramFrontend Engineer106.5
Maya OrenFrontend Engineer46.7
Lior DaganQA Engineer23
Adi RosenDevOps Engineer8.8
Nir FeldProduct Manager5.6
Ella ShavitProduct Designer14.8
Yael MaromData Analyst18.7
Eran GoldHead of Sales19.5
Noa FriedmanSDR37
Ben TzurAccount Executive18
Dana KatzCustomer Success Manager25.8
Yuval SternSupport Engineer64.5
Shir AdlerMarketing Manager6.7
Tomer AloniContent Writer21.2
Tamar LeviFinance & Ops Manager14
Dor ElkayamOffice Manager & HR7.3
Heaviest branch: Alon Peled · 489.5 h/moInterviewed: 20 of 20Mapped total: 489.5 h/mo

Mapped processes

49

Feature ticket development (e.g., filters panel)

Gil Baram · Frontend Engineer · R&D
Low
Tool chain
Linear→GitHub
Hours / mo100 h · 100 h
largest single mapped process
Automation ideaAutomate the production release trigger (e.g., scheduled or one-click deploy pipeline) to remove the manual end-of-week release step, though the core coding and review work remains human-driven.

Repeat ticket handling in Intercom

Yuval Stern · Support Engineer · Customer Success
Medium
Tool chain
Intercom
Hours / mo55 h · 55 h
of 100 h max
Automation ideaBuild an auto-updating knowledge base or AI-assisted reply suggestion tool in Intercom that surfaces the most current verified answer for common questions, reducing manual search-and-reword time.

Bug fix and PR workflow

Maya Oren · Frontend Engineer · R&D
Low
Tool chain
GitHub→Jira
Hours / mo36 h · 36 h
of 100 h max
Automation ideaAutomate PR review reminders and deployment status notifications, though the core reproduction and coding work remains manual and judgment-driven.

Post-build regression testing and bug ticketing

Lior Dagan · QA Engineer · R&D
Medium
Tool chain
Slack→Google Sheets→Jira
Hours / mo19 h · 19 h
of 100 h max
Automation ideaBuild an integration that auto-creates a Jira ticket with pre-filled repro steps and screenshots directly from a failed row in the Google Sheet, and route it based on a predefined area-ownership mapping.

Follow-up Email Sequence & Lead Handoff to Eran

Noa Friedman · SDR · Sales
High
Tool chain
HubSpot→Notion→Slack
Hours / mo18 h · 18 h
of 100 h max
Automation ideaSet up an automated HubSpot email sequence for the two follow-ups and auto-generate the Notion handoff note with a Slack alert when a lead qualifies.

Research and draft new blog posts

Tomer Aloni · Content Writer · Marketing
Low
Tool chain
Google Docs→Slack→Notion
Hours / mo16 h · 16 h
of 100 h max
Automation ideaProvide an AI drafting assistant fed by a knowledge base of past posts and product docs to auto-generate a first-draft outline and reduce manual research time.

Automatable hours by department

R&D holds 47% of the mapped time
R&D · 229.4 h
Customer Success · 90.3 h
Sales · 74.5 h
39.1
27.9
R&D229 h229.4 h · 7 people · 47%
Customer Success90 h90.3 h · 2 people · 18%
Sales75 h74.5 h · 3 people · 15%
Product39 h39.1 h · 3 people · 8%
Marketing28 h27.9 h · 2 people · 6%
Time on the table · Kite Systems7,472 hautomatable hours per yearThe same as 3.6 of one full time person, every month.
Automatable hours mapped489.5 h / mo
Ad-hoc interruptions at 50%133.1 h / mo
Monthly cost0 h
× 12 months7,472 h
Basis: 49 processes mapped across all 20 employees. Hours are employee-estimated per month.
Feature ticket development (e.g., filters panel) · Gil Baram1,200 h
Repeat ticket handling in Intercom · Yuval Stern660 h
Bug fix and PR workflow · Maya Oren432 h
Post-build regression testing and bug ticketing · Lior Dagan228 h
Follow-up Email Sequence & Lead Handoff to Eran · Noa Friedman216 h
Research and draft new blog posts · Tomer Aloni192 h
Inbound Lead Research & CRM Entry · Noa Friedman180 h
All other mapped processes · 42 processes, 230.5 h/mo0 h
Mapped processes subtotal5,874 h
Ad-hoc interruptions at 50% · 133.1 h/moself-reported, no mapped process1,598 h
Total per year7,472 h

Scope scenarios

range = 70-90% realization

Scopes cover mapped processes only. Ad-hoc interruptions (133.1 h/mo, 1,598 h per year) are counted in the headline figure but belong to no single scope.

Where it breaks

Every point in the mapped work where someone said something goes wrong or gets redone, in their words. Ranked by the size of the process it sits inside.

  • Feature ticket development (e.g., filters panel)Gil Baram · 100 h a month

    CI occasionally flakes and needs a re-run; no dedicated QA so bugs may slip through since developers test their own work

    No dedicated QA step, manual production release process, occasional CI flakiness requiring re-runs

  • Repeat ticket handling in IntercomYuval Stern · 55 h a month

    Copying an outdated answer (e.g., an old setup step that changed) causes customer confusion and requires follow-up corrections

    Manually searching for and rewriting the same answers repeatedly instead of having them ready; risk of reusing outdated information

  • Bug fix and PR workflowMaya Oren · 36 h a month

    Bugs that can't be reproduced or turn out to be backend issues stall the fix process

    Fix time varies widely, from an hour for small bugs to a day or two for bigger ones, making workload unpredictable

  • Post-build regression testing and bug ticketingLior Dagan · 19 h a month

    Tickets bounce between owners when a bug spans two functional areas and ownership is unclear

    Manual re-testing and manual ticket writing for every build; ownership ambiguity causes delays

  • Follow-up Email Sequence & Lead Handoff to EranNoa Friedman · 18 h a month

    Second follow-up email is often forgotten due to no reminder system

    No reminder mechanism for the second follow-up email, leading to missed touches

  • Research and draft new blog postsTomer Aloni · 16 h a month

    None mentioned

    No formal review process; research and drafting take a large chunk of time (4 hours per post)

How this report is built
InterviewsEach employee talks through a real workday, 15 minutes on their phone.
Processes mappedEvery repetitive task is captured with tools, frequency and hours.
Cross-person synthesisChains that span people are stitched together and priced.
Automation planRanked candidates become a concrete proposal with a payback figure.

Interviews

20 · 49

This is a live, private report link for your company. Anyone with the link can view it, so share it only inside your team.