# Chronoguild

*/Startups/Chronoguild*

## Startup Overview

This system indexes integrated development environment (IDE) events to generate cryptographically signed timesheets. By running locally during coding sessions, it captures keystrokes, commits, and file modifications to build a continuous log of development activity without requiring start-stop timers.

Freelance software engineers and technical contractors face persistent friction when tracking billable hours and justifying time spent to clients. Standard time logging requires constant context-switching and relies on human memory, leading to lost billable minutes and frequent billing disputes.

While tools like Toggl Track, Clockify Enterprise, and the Upwork Desktop App rely on manual inputs or invasive screen recording, this solution is passive-capture native. It eliminates manual entry entirely by cryptographically verifying the actual development work as it happens, delivering an immutable proof-of-work record.

## Startup Founding Hypothesis

**Approach**: that indexes IDE events to generate cryptographically signed timesheets
**Competitors**:
- [Toggl Track](/Competitors/Toggl_Track)
- [Clockify Enterprise](/Competitors/Clockify_Enterprise)
- [Upwork Desktop App](/Competitors/Upwork_Desktop_App)
**Differentiator2x2**: passive-capture native and cryptographically verified, eliminating manual entry completely

## Startup Solution Coordinate

**Solution**: [Chronoguild Ledger](/Software/Chronoguild_Ledger)

## Startup Position2x2

```mermaid
quadrantChart
    x-axis Manual Entry --> Passive Capture
    y-axis Honor System --> Cryptographically Verified
    Toggl Track: [0.15, 0.20]
    Clockify Enterprise: [0.30, 0.35]
    Upwork Desktop App: [0.85, 0.45]
    Chronoguild: [0.90, 0.85]
```

## Startup Offer

**Proof**:
- Targeting freelance software engineers aiming to recover 3+ hours of lost billable time per week.
- Aiming to help development agencies eliminate client invoice disputes through immutable activity logs.
- Designed for enterprise compliance teams seeking zero-manual-entry audit trails for external contractor hours.
**Tiers**:
- Name: Solo Developer · Price: ~$12–$25/mo · Inclusions: Passive IDE activity indexing for a single user, local event hashing, and up to 50 cryptographically signed timesheet exports per month.
- Name: Agency Team · Price: ~$30–$55/user/mo · Inclusions: Unlimited verifiable timesheets, aggregated team billing dashboards, and designed to integrate with Jira and GitHub for cross-referenced issue tracking.
- Name: Enterprise Ledger · Price: Custom: ~$15k–$40k/yr base · Inclusions: Continuous cryptographic ledger sync, dedicated SSO, compliance audit trails for large contractor fleets, and intended API access for custom billing pipelines.
**Guarantee**: Chronoguild guarantees that cryptographically signed timesheets will accurately reflect active IDE time; if an exported log drops recorded, active sessions and causes a billing discrepancy, your current month of service is fully refunded.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: 'Will indexing keystrokes and events slow down my IDE?' Rebuttal: The capture engine runs asynchronously as a background process, ensuring zero noticeable latency in your primary development environment.
- Objection: 'Does this upload my proprietary source code to your servers?' Rebuttal: Chronoguild only hashes metadata and timestamps locally; your actual code never leaves your machine.
- Objection: 'What if I spend two hours whiteboarding or in meetings?' Rebuttal: Users can manually append offline blocks to the timeline, which are clearly demarcated as self-reported rather than cryptographically verified.
- Objection: 'Clients might not understand what a cryptographic timesheet is.' Rebuttal: The exported PDF includes a plain-English summary of hours worked alongside a simple verification link to prove the document's authenticity.
**Pricing Architecture**: Tiered
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Authoritative and developer-native, communicating with stark precision about verifiable proof.
**Tagline**: Provable timesheets generated passively from your background IDE activity.
**Icon Concept**: stamp
**Palette Intent**: electric-signal
**Visual Identity**: The aesthetic pairs deep terminal black with sharp syntax-highlight green and strict monospace typography to evoke immutable cryptographic logs.
**Archetype Reference**: the-sage

## Startup Buyer Chain

**Chain**: Chronoguild → Freelance Developer → Enterprise Client
**Gtm Motion**: Acquires individual developers through a self-serve tier to eliminate their manual time tracking overhead. Expands virally when these developers submit cryptographically verified timesheets to enterprise clients, leading those clients to mandate the tool across their entire contractor pool.
**Agent Channel**: Intended for registry in LangChain tool catalogs and automated procurement API directories, enabling AI project managers and billing agents to query verified IDE work logs natively.
**Primary Channel**: Organic search discovery within the VS Code Marketplace and JetBrains Plugin Repository when developers look for time tracking or automated billing extensions.

## Startup Customer Journey

```mermaid
flowchart LR;A[VS Code Marketplace]-->B[Chronoguild IDE Extension];B-->C[Local Metadata Hash];C-->D[Cryptographic Timesheet];D-->E[Client Invoice];E-->F[Contractor Pool];F-->G[Enterprise Ledger API];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- A 14-day solo pilot measuring the delta between manually reported hours and passively indexed IDE activity, aiming to prove a net increase in captured billable time.
- A 30-day team deployment across a development agency testing Jira and GitHub cross-referencing, aiming to generate cryptographically verified invoices without a single client rejection.
- A 60-day integration test with an enterprise contractor fleet validating the API billing pipeline, aiming to prove local event hashing correctly anonymizes source code while maintaining accurate ledger syncs.
**Target Metrics**:
- Aim: 3 additional hours of previously unbilled micro-tasks recovered per developer per week.
- Target: 100 percent reduction in client disputes regarding billed development hours.
- Aim: Zero milliseconds of noticeable latency added to the local IDE environment during background hashing.
- Target: Zero lines of proprietary source code transmitted to external servers during timeline generation.
**Target Case Studies**:
- A freelance software engineer replacing manual end-of-week time estimation with continuous IDE event hashing to capture previously forgotten micro-tasks and increase weekly billable hours.
- A mid-sized development agency adopting immutable activity logs for client billing to shift from contested invoice hours to auto-verified timesheets that eliminate client disputes.
- An enterprise compliance team managing external developers replacing self-reported contractor hours with a continuous cryptographic ledger sync to establish a zero-manual-entry audit trail for vendor payments.
**Testimonial Targets**:
- A freelance senior developer stating they no longer underbill because the background capture engine accurately logs every active IDE session automatically.
- An agency founder confirming that the cryptographically signed PDF exports provide instant trust with their clients and make invoice processing immediate.
- A vendor management director expressing confidence in the compliance audit trails because the verifiable ledger removes the need to manually audit contractor timesheets.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Enterprise security teams classify the IDE telemetry agent as a data exfiltration threat and block deployment across organizational networks. · Mitigation Status: unmitigated
- Severity: high · Description: Major IDE publishers like Microsoft or JetBrains restrict extensions from accessing low-level editor events, severing the core data pipeline. · Mitigation Status: in-progress
- Severity: moderate · Description: Malicious users develop scripts to simulate keystrokes and file modifications within the IDE, successfully spoofing the cryptographic timesheet signatures. · Mitigation Status: in-progress
- Severity: low · Description: Independent contractors reject passive tracking due to privacy concerns, opting for the opacity of manual billing via Toggl or Clockify. · Mitigation Status: unmitigated

## Startup Competitors

- [Toggl Track](/Competitors/Toggl_Track) — Manual Entry
- [Clockify Enterprise](/Competitors/Clockify_Enterprise) — Enterprise Incumbent
- [Upwork Desktop App](/Competitors/Upwork_Desktop_App) — Screenshot Monitoring
- [WakaTime](/Competitors/WakaTime) — Developer Analytics
- [Manual Spreadsheets](/Competitors/Manual_Spreadsheets) — Status Quo

## Startup Solution Stack

- [Verified Timesheet Service](/Services/Verified_Timesheet_Service) — Service-as-Software
- [IDE Telemetry Agent](/Agents/IDE_Telemetry_Agent) — Agent
- [Time Allocation Worker](/Agents/Time_Allocation_Worker) — Agent
- [Cryptographic Signature Engine](/Software/Cryptographic_Signature_Engine) — Software
- [Local Event API](/Software/Local_Event_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to stand as an unimpeachable professional who bills for actual output, not estimates
- **Want**: to recover every billable hour without the friction of manual time tracking
- **Identity**: a freelance software engineer or agency lead
**Plan**:
- Step: Develop · Detail: Write code as usual in VS Code or IntelliJ while the engine indexes local metadata.
- Step: Approve · Detail: Review the generated timeline of active sessions to confirm the daily billable totals.
- Step: Export · Detail: Generate a signed PDF timesheet that provides immutable proof of work for your client.
**Guide**:
- **Empathy**: You shouldn't still be guessing how many hours you spent in the terminal. Toggl Track wasn't built to index IDE events at the kernel level.
**Problem**:
- **Villain**: manual session logging
- **External**: tracking hours in Toggl Track requires constant toggling that fails to capture the fragmented nature of VS Code or IntelliJ sessions
- **Internal**: you feel like a clock-watcher instead of a builder, constantly second-guessing if you shortchanged your own invoice
- **Philosophical**: Why should a developer accept the loss of billable time when digital activity is naturally immutable?
**Success**: Every second of IDE activity is captured passively, resulting in invoices that clients pay without question.
**One Liner**: Every week, software engineers lose billable time to manual logging. Chronoguild generates signed timesheets from background IDE activity so developers get paid for every second of work.
**Positioning**:
- **So That**: eliminate manual entry with passive, verifiable IDE activity logs
- **Unlike**: Toggl Track or Clockify
- **For Whom**: freelance engineers and dev agencies
- **Category**: Cryptographic time tracking for developers
**Call To Action**:
- **Direct**: Generate signed timesheet
- **Transitional**: View sample cryptographic log
**Failure Stakes**:
- losing three hours of billable time weekly
- awkward invoice disputes with clients
- underreporting high-intensity coding sessions
**Transformation**:
- **To**: free to focus on architecture, no longer stuck in stopwatch drudgery
- **From**: a developer guessing hours on a Friday afternoon
**Controlling Idea**: Cryptographically verifiable work eliminates the need for manual time tracking.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Every week, software engineers lose billable time to manual logging. Chronoguild generates signed timesheets from background IDE activity so developers get paid for every second of work.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: f5b4ccc33ddc05c4

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Cryptographic time tracking for developers for freelance engineers and dev agencies. Unlike Toggl Track or Clockify — eliminate manual entry with passive, verifiable IDE activity logs.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: e41028084f10a9ad

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: tracking hours in Toggl Track requires constant toggling that fails to capture the fragmented nature of VS Code or IntelliJ sessions
Solution: Every week, software engineers lose billable time to manual logging. Chronoguild generates signed timesheets from background IDE activity so developers get paid for every second of work.
Customer: freelance engineers and dev agencies
Unlike: Toggl Track or Clockify
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 15334825ec1a78c9

## Startup Token M E D D P I C C

**Pain**: tracking hours in Toggl Track requires constant toggling that fails to capture the fragmented nature of VS Code or IntelliJ sessions
**Metrics**: Target: Every second of IDE activity is captured passively, resulting in invoices that clients pay without question.
**Rendered**: Pain: tracking hours in Toggl Track requires constant toggling that fails to capture the fragmented nature of VS Code or IntelliJ sessions
Economic buyer: Freelance Developer
Metrics: Target: Every second of IDE activity is captured passively, resulting in invoices that clients pay without question.
Competition: Toggl Track or Clockify
**Mechanism**: spine-derived-v1
**Competition**: Toggl Track or Clockify
**Economic Buyer**: Freelance Developer
**Vocab Fingerprint**: d294c9e1f9abcf25

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Cryptographic time tracking for developers for freelance engineers and dev agencies

freelance engineers and dev agencies — tracking hours in Toggl Track requires constant toggling that fails to capture the fragmented nature of VS Code or IntelliJ sessions Every week, software engineers lose billable time to manual logging. Chronoguild generates signed timesheets from background IDE activity so developers get paid for every second of work.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: f28a4a03cfe4aedd

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Cryptographic time tracking for developers. Every week, software engineers lose billable time to manual logging. Chronoguild generates signed timesheets from background IDE activity so developers get paid for every second of work. Serves freelance engineers and dev agencies.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 26c34d9c59c1357c

## Neighborhood

### Candidate solutions

- [Untangle Intercompany Eliminations](/Problems/Untangle_Intercompany_Eliminations) — candidate solution for · Problems

### What it offers

- [Chronoguild Ledger](/Software/Chronoguild_Ledger) — offers · Software

### Composed of

- [Verified Timesheet Service](/Services/Verified_Timesheet_Service) — composes · Services
- [IDE Telemetry Agent](/Agents/IDE_Telemetry_Agent) — composes · Agents
- [Time Allocation Worker](/Agents/Time_Allocation_Worker) — composes · Agents
- [Cryptographic Signature Engine](/Software/Cryptographic_Signature_Engine) — composes · Software
- [Local Event API](/Software/Local_Event_API) — composes · Software

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Competitors

- [Toggl Track](/Competitors/Toggl_Track) — competes with · Competitors
- [Upwork Desktop App](/Competitors/Upwork_Desktop_App) — competes with · Competitors
- [Clockify Enterprise](/Competitors/Clockify_Enterprise) — competes with · Competitors
- [WakaTime](/Competitors/WakaTime) — competes with · Competitors
- [Manual Spreadsheets](/Competitors/Manual_Spreadsheets) — competes with · Competitors

### Similar Startups

- [Timust](/Startups/Timust) — similar · Startups
- [Unbillablegrain](/Startups/Unbillablegrain) — similar · Startups
- [Gainunbillable](/Startups/Gainunbillable) — similar · Startups
- [Unbillablecity](/Startups/Unbillablecity) — similar · Startups
- [Unbillablewrap](/Startups/Unbillablewrap) — similar · Startups
- [Unbillableion](/Startups/Unbillableion) — similar · Startups
- [Calarvest](/Startups/Calarvest) — similar · Startups
- [Directorunbillable](/Startups/Directorunbillable) — similar · Startups
- [Zerounbillable](/Startups/Zerounbillable) — similar · Startups
- [Billablebilling](/Startups/Billablebilling) — similar · Startups
- [Scanunbillable](/Startups/Scanunbillable) — similar · Startups
- [Unbillableaura](/Startups/Unbillableaura) — similar · Startups
- [Cleanunbillable](/Startups/Cleanunbillable) — similar · Startups
- [Billablehaze](/Startups/Billablehaze) — similar · Startups
- [Unbillablefire](/Startups/Unbillablefire) — similar · Startups
- [Unbilledmonth](/Startups/Unbilledmonth) — similar · Startups
- [Unbillablestar](/Startups/Unbillablestar) — similar · Startups
- [Unbillabletile](/Startups/Unbillabletile) — similar · Startups
- [Laurel](/Startups/Laurel) — similar · Startups
- [Billableloft](/Startups/Billableloft) — similar · Startups