Product strategy · Workflow · Reliability

    Jobio

    Turn an oversized SaaS into a clear next commercial action.

    Jobio helps a tech freelancer decide what to do today to move toward the next engagement. The redesign replaced an all-in-one suite with five core areas and a testable workflow.

    Role
    Solo product strategy, UX, architecture and full-stack development
    Period
    2026 scope reduction
    Status
    Functional core · commercial validation pending
    Jobio — interface principale

    Verifiable evidence

    399/399

    active tests

    Three historical auto-save tests remain skipped

    5

    core areas

    Today, Pipeline, Follow-ups, CV, Contacts

    3 max

    daily priorities

    Impact, urgency and context remain visible

    137

    build routes

    Reference production build

    How to read the numbers : Evidence covers local operation and tests; no commercial conversion is claimed yet.

    Context and role

    The product had accumulated CRM, billing, public profiles, platforms, programs, analytics and AI assistants. That breadth blurred the promise and made every screen expensive to finish.

    The retained need is narrower: capture an opportunity, see the next action, follow up without over-contacting and tailor a CV.

    Finishing started with one source of truth for scope, followed by high-risk mutations: Kanban, follow-ups, contact merge and CV export.

    Retained constraints

    • A hidden module must be inaccessible through navigation, deep links and pricing.
    • Optimistic Kanban movement must be undoable and resist double actions.
    • Follow-ups must stop after response, opt-out, terminal mission or excessive cadence.
    • Contact merge must preserve relationships and never silently overwrite a field.
    • CV export must remain ATS-readable and stable on A4.

    Decisions and rejected options

    DECISION 01

    A server manifest to cut scope

    Hiding a link does not remove a route, price or server action.

    Choice
    Navigation, deep links, pricing and server checks consume the same active, hidden or beta status.
    Rejected
    Finishing every historical module or hiding them with CSS.
    Trade-off
    Some code remains temporarily present but inaccessible while V1 is validated.
    DECISION 02

    Conditional Kanban transitions

    Fast concurrent actions could produce stale status or inconsistent counters.

    Choice
    The mutation compares expected status, is replayable, updates atomically and offers undo then retry.
    Rejected
    A blind mutation followed by a full refresh.
    Trade-off
    More conflict logic for an instant UI that keeps data coherent.
    DECISION 03

    One follow-up policy

    Manual actions, rules and sequences used different safeguards.

    Choice
    One domain function blocks duplicates within 24 hours, three touches in seven days, replies, opt-outs and terminal statuses.
    Rejected
    Checks scattered across each form and cron.
    Trade-off
    Some automation intentionally stops earlier to protect the relationship.
    DECISION 04

    Preview before merge

    A known email may carry complementary or conflicting information.

    Choice
    Fields are compared and the user either keeps both records or explicitly merges before a relational transaction.
    Rejected
    Automatically overwrite the oldest contact.
    Trade-off
    One extra decision prevents silent data loss.

    Journey architecture

    1. 01

      Feature manifest

      One server source drives availability, navigation and offering.

    2. 02

      Today

      No more than three actions aggregated from missions and follow-ups.

    3. 03

      Pipeline

      Kanban/list views with conditional optimistic transitions.

    4. 04

      Follow-up policy

      Shared safeguards across actions, rules and sequences.

    5. 05

      CV renderer

      Master profile, overrides, then deterministic A4 and ATS outputs.

    Quality and verification

    • Kanban mutation tested for no-op, conflict, undo and auxiliary failure.
    • Follow-up policy covered across every stop reason.
    • Transactional merge of missions, interactions, emails, companies and tags.
    • ATS export without photos, columns, decoration or hidden sections.
    • Persistent four-step onboarding resumable from server state.
    Jobio — vue produit

    What is actually delivered

    • Navigation reduced to five areas and a Today page focused on action.
    • An optimistic, undoable pipeline coherent under concurrent updates.
    • Follow-ups protected against duplicates and over-contacting.
    • Duplicate preview before creation or merge.
    • Deterministic ATS CV export alongside A4 preview.

    Known limits

    • The gate of five real freelancers, with two willing to continue or pay, is not reached.
    • LinkedIn duplicate detection and reversible merge history remain to build.
    • A4 PDF still needs a long-corpus and production-engine check.
    • Saved filters/views and ownership E2E remain incomplete.

    Next step

    • Have five freelancers run the timed onboarding and five core journeys.
    • Add per-channel delivery journal and merge restoration.
    • Validate one Pro plan in Stripe test mode before any live catalogue change.

    Technical foundation

    • Next.js 16
    • React 19
    • TypeScript
    • Prisma
    • PostgreSQL
    • Server Actions
    • Playwright
    • Stripe