Try the Work

The company appears to be a solo project named "Try the Work", self-described as a platform that turns authorized job descriptions into AI-augmented mini-shifts for candidates to practice before applying. The author states this is built with TypeScript and submitted to the OpenAI 2026 hackathon.

What changed: The project evolved from an earlier effort called "Harmony", which explored how humans and intelligent tools can grow together without losing agency, into a practical tool focused on job preparation through realistic, evidence-based practice.

The single most important open question: Is there any evidence of traction, revenue or customer adoption beyond the author's own development work?

Analysis basis: This report is based entirely on the self-reported project description provided by the caller. No external verification or historical data is available. All claims are attributed to the author’s own account and should be treated as unverified.

• The description states that Try the Work turns an authorized job description into a realistic, AI-augmented mini-shift.
• Learners perform observable work using AI assistance (with optional local Ollama support).
• It outputs a candidate-owned "Work Receipt" with source citations, scored evidence, improvement recommendations, and explicit untested gaps.
• The system separates supported requirements from assumptions and checks observable evidence rather than personality traits.
• Human review is required before exporting any learner-owned receipt or deeper Codex work packet.

Inference: The product appears to be a prototype or proof-of-concept for job rehearsal using AI, focused on transparency and human control in the process. It does not appear to have a live product or marketplace yet.

• The author states that Try the Work applies a philosophy from prior work ("Harmony") around keeping human judgment visible, carrying evidence with claims, and making learning lead to real capability.
• It positions itself as a safer way for candidates to practice before applying, and as a foundation for fairer, job-relevant tryouts for hiring teams.
• The author also frames it as supporting uptraining and cross-training without pretending one exercise measures a whole person.

Inference: The positioning has evolved from abstract exploration of human-AI collaboration to a concrete tool focused on job readiness and hiring fairness. However, no evidence suggests this has moved beyond the author’s own development or hackathon submission.

• For candidates: A way to practice before applying, showing what they can actually do.
• For hiring teams: A foundation for fairer, job-relevant tryouts.
• For employers: Support for uptraining and cross-training without pretending one exercise measures a whole person.

Not evidenced: No information is provided about specific customer segments, personas, or whether the product targets any particular industry or role type beyond general job descriptions.

• The description does not mention pricing, subscriptions, or monetization strategies.
• It mentions that the included shift runs without an API key or paid model.
• Optional Ollama support stays on numeric loopback and cannot take outside action.
• Codex is described as a deeper build-and-improve path, but no details are given about costs or access models.

Not evidenced: No evidence of business model, pricing tiers, or monetization strategy beyond the author’s own development work.

• Built with TypeScript.
• The system reads only the authorized role source.
• Separates supported requirements from assumptions.
• Uses deterministic guidance and optional localhost-only Ollama assistance.
• Requires human review before exporting results.
• Includes a reproducible local build and optional offline-assistance path.
• Has 17 focused tests covering various aspects like state, citations, math, prompt-like text, unsupported claims, hashes, approval, local lessons, and runtime-mode contracts.

Inference: The technical architecture is described as bounded and deterministic, with an emphasis on human control and transparency. There is no indication of scalability or production deployment beyond the author’s own testing.

• The project was submitted to the OpenAI 2026 hackathon.
• It includes a working end-to-end mini-shift.
• It has 17 focused tests covering multiple areas.
• It is described as a "reproducible local build and optional offline-assistance path."

Not evidenced: No evidence of revenue, customer adoption, usage metrics, or any form of traction beyond the author’s own development.

• The description does not reference competitors or similar products.
• It does not state whether there are existing platforms for job rehearsal or AI-augmented skill practice.

Not evidenced: No competitive landscape is described. No evidence of market presence or differentiation from other tools.

• The project is a solo effort (team size: 1).
• It has no verified traction, revenue, or customer base.
• The product is described as a prototype or hackathon submission with no indication of production readiness.
• There is no mention of scalability, data privacy, or compliance considerations.
• The author retains all product, identity, claims, approval, and release decisions — suggesting limited external validation.

Inference: The lack of team, traction, and commercialization signals a high risk of failure to scale or gain market adoption without significant additional development or investment.

1. What is the intended path from this prototype to a scalable product?
2. How does the project plan to address concerns around data privacy, especially with AI-assisted job practice?
3. Are there any plans for monetization or customer acquisition beyond the author’s own development?
4. Has the author considered how to validate that the mini-shifts accurately reflect real-world job tasks?
5. What are the key assumptions about user behavior and adoption in the hiring process?