Weekform

• The description states that Weekform is a local-first macOS workload intelligence app.
• It aggregates signals from:
  • Calendars
  • Applications
  • Chat activity
  • Git history
  • Local imports
• These are turned into reviewable work blocks.
• Users can confirm, relabel, annotate, or exclude those blocks before they affect the workload model.
• The app estimates:
  • Planned and reactive workload
  • Recurring commitments
  • Fragmentation and carryover risk
  • Reliable capacity for new work
• It includes optional AI-assisted features such as classification, forecasts, summaries, and workload questions.
• The core capacity model is described as deterministic and inspectable.
• Users can optionally share approved weekly aggregates with a team; raw activity or unreviewed evidence are not shared.

Note

The description does not state whether the product has been released to users, tested in production, or used by anyone beyond the authors. It is self-reported as a functioning prototype.

• The tagline: “Weekform turns the work you actually do into a clear view of workload, risk, and capacity, helping you protect focus and know what fits before you commit.”
  • This positions Weekform as a planning tool that helps users understand their real workload.
• The inspiration section states:
  • Calendars show scheduled time. Task trackers show planned work.
  • Neither reflects the full reality of knowledge work, where interruptions, chat requests, recurring tasks, and unfinished projects compete for capacity.
  • Weekform aims to help people understand what is already in motion and what can realistically fit next.
• The product is described as a private planning tool, not a timesheet or surveillance system.
• It emphasizes:
  • User control over what is reviewed, corrected, and shared
  • Transparency in workload modeling
  • AI-assisted features that are optional and human-reviewed

Inference The positioning evolved from addressing a gap in traditional tools (calendars, task trackers) to offering a more nuanced view of workload through local activity signals and deterministic models.

• The description states that Weekform is designed for knowledge workers.
• It targets users who:
  • Work with fragmented signals from calendars, applications, chat, Git
  • Need clarity on what fits next in their schedule
  • Want to protect focus and make informed decisions about workload
• It is described as a private planning tool, not a team or management system.
• The team experience includes:
  • Shared snapshots
  • Manager dashboards
  • Team Briefing
  • Approval gates for AI-assisted actions

Note

No specific customer personas, segments, or market size are mentioned. The description does not indicate whether the product is aimed at individuals, teams, or managers.

• Not evidenced.
• The description does not mention:
  • Revenue model
  • Pricing structure
  • Subscription tiers
  • Freemium vs paid features
  • Monetization strategy

Absence of evidence

There is no indication of how the product would generate revenue or whether it has a defined business model.

• Built with:
  • Tauri (for desktop app)
  • React, TypeScript, Rust
  • Next.js (web experience)
  • Supabase (authentication, teams, invitations, shared snapshots)
  • Codex (powered by GPT-5.6) for development assistance
• The app handles:
  • Local activity review
  • Workload modeling
  • Forecasting
  • Privacy controls
• Shared packages process signals, group sessions, calculate capacity, and manage approved data sharing.
• The team includes:
  • Kyle Springfield (product direction, Mac experience, privacy model, workload design)
  • Rohn Springfield (web application, deployment, authentication, team workflows)

Note

The technical stack is described in detail, but there is no evidence of performance metrics, scalability, or production usage.

• Not evidenced.
• The description does not mention:
  • Users
  • Customers
  • Revenue
  • Product adoption
  • Market feedback
  • Growth metrics
  • Product maturity beyond prototype stage

Absence of evidence

No traction or user engagement data is provided. The product is described as a functioning prototype, but no real-world usage is indicated.

• Not evidenced.
• The description does not mention:
  • Competitors
  • Market positioning relative to others
  • Product differentiation
  • Industry trends
  • Use cases or market gaps addressed

Absence of evidence

No competitive landscape or context is provided. The authors do not reference existing tools or markets.

• Unverified claims: All information is self-reported and unverified.
• No traction or users: The product is described as a prototype with no evidence of real-world usage.
• AI dependency: Reliance on Codex (GPT-5.6) for development may raise questions about scalability, control, and long-term viability.
• Privacy vs usability trade-offs: While privacy is emphasized, the app’s utility depends on accurate inference from fragmented signals — a balance that may be difficult to maintain.
• Limited scope: The product is described as macOS-only with a web experience, which may limit its appeal or scalability.
• Unclear monetization: No business model or pricing strategy is evident.

Inference If the product is not yet used by real users, it may be premature to assess its effectiveness or market fit.

1. What specific user feedback have you received so far?
2. How do you plan to validate your workload model with actual users?
3. Are there any early adopters or pilot users of the product?
4. What is your roadmap for expanding beyond macOS and into other platforms or workflows?
5. How do you intend to monetize this product, if at all?
6. What are the key assumptions in your capacity estimation model, and how will they be tested?
7. How does the AI-assisted development process affect long-term maintainability and control?
8. What is the current state of the Mac signing and distribution process?