Direction & roadmap
Iterune is being developed as a structured, long-term record of work, life and administration. Focused apps sit on top of connected information so people can enter less, retrieve more and turn history into useful actions.
Purpose
Each domain should provide a focused workflow while contributing to a durable record that can be reused elsewhere. The long-term advantage is not the number of screens Iterune has; it is that information entered today can still save work, answer questions and trigger useful actions years later.
Product laws
Information should become reusable across future workflows instead of being repeatedly re-entered.
Imports, extraction and relationships should do more of the organisational work than manual upkeep.
Stored information matters when connections produce retrieval, reminders, signals and useful next steps.
A month of records should be useful. A year should be substantially more useful.
AI can extract, retrieve, compare and draft, but structured facts stay inspectable, correctable and attributable.
Privacy, security, provenance, export, deletion and recovery are product capabilities, not background chores.
Current status
Direction
New breadth should unlock when the previous layer is genuinely useful. The focused Career apps prove independent usefulness and shared records. Documents provides evidence. Shared records connect information. Search and attention make history useful. Imports reduce maintenance. A second deep vertical then tests whether the model generalises.
Architecture
Shared data should not become one giant abstract schema. Domains own meaningful records; common services and explicit relationships connect them.
Discovery, high-intent content, Blog, Community and clear product status. Public messaging should explain the value of connected history rather than promise a vague everything-in-one-place suite.
An overview and launch point, not a duplicate of every app. It should increasingly surface useful cross-app attention and history.
Career is a section containing Applications, Career Record and Professional Development. Focused apps own workflows and canonical domain records.
Connect, Documents, Document Studio, managed Mail, entities, relationships, search, Calendar, reminders, provenance, imports, sharing and account/security services are reused across domains.
Supabase-backed identity, PostgreSQL records, private storage, RLS and explicit permissions. Shared concepts connect domains without forcing every record into one generic schema.
Domain fact
A job, application, vehicle or qualification belongs to its domain.
Evidence
Documents support facts and can be reused across workflows without duplication.
Relationship
Explicit links make organisations, people, dates, costs and records useful across domains.
High-level version release plan
This is directional rather than a promise of fixed dates. Ordering can change when real usage produces better evidence.
Build the first complete Iterune product while extracting the shared infrastructure the rest of the platform will reuse.
Turn Documents from a file manager into the evidence layer underneath Iterune.
Formalise only the shared concepts proven necessary by real use.
Make accumulated information easy to retrieve across domains and over time.
Surface what needs attention from underlying records instead of becoming another task manager.
Reduce typing and make existing information the starting point.
Use enough real data to suggest connections and actions with evidence.
Prove that the Iterune model generalises beyond Career before expanding broadly.
Combine multiple areas temporarily when a real event spans them.
Create value that only exists because useful history has accumulated.
Make conversation an interface to the user's structured history, not the product itself.
Make security, control and portability visible product strengths.
Extend the proven single-person model without weakening private-by-default behaviour.
Let external systems contribute to or consume authorised Iterune records safely.
Expand only where the shared platform creates a real advantage.
Reserve 1.0 for proof of the product thesis, not simply for being publicly available.
Near-term execution
Build repeatable Connect relationships/provenance and fix structural database debt before adding more Career-specific shortcuts.
Extract shared document primitives from the CV system without breaking existing CV behaviour; prove the abstraction with cover letters.
Make one canonical, editable Career History and make CV import the fastest path into it.
Create the first unified discovery layer with saved searches, user-controlled imports and provider adapters that only use permitted access.
Make one Job page the place to understand compensation, practical fit, commute, evidence match, market context and whether the role deserves an application.
Separate opportunities from submitted applications, add a clear progress rail and preserve exact materials, events, correspondence, feedback and outcomes.
Lay the shared Iterune Mail foundation so administrative correspondence can become linked records, Calendar events, reminders and attention items rather than another inbox.
Simplify Career navigation and then audit public/product copy, links, capitalisation, formatting and maturity claims across the website.
Measure imports, reuse, opportunity decisions, applications, retrieval success, useful attention actions and 30/90/180-day return behaviour.
Continue RLS, storage, deletion/export, recovery, provenance and security work alongside product features rather than postponing it.
Opportunities
What not to become
Measure behaviour
A records product can be valuable without daily engagement. Measure whether people get useful results, reuse their history and return when that history matters.
Trust & notes
Career first. The wider platform should support Career rather than slow it down.
Documents are infrastructure with a user-facing app. They should become the evidence layer used everywhere else.
Vehicle is a candidate, not a commitment. The second deep vertical should be selected from evidence.
Money comes with a higher bar. Iterune can store domain costs before becoming a financial aggregation product.
AI is an input and assistance layer. Provenance, correction and deterministic logic remain important.
Portability matters. Retention should come from useful history, not from making that history difficult to leave with.
This roadmap can change. Product maturity and real behaviour should outrank an old plan.
Long-term proposition
The goal is not to replace every specialist tool. It is to make important information durable, connected, reusable and increasingly useful as a person's history grows.