Product Architecture

Every capability, which tier it belongs to, and whether it actually exists. Anything marked built links to the route where it runs.

12 of 18 capabilities are built. 6 are not.

The unbuilt six are the ones that would justify the Pro and Studio tiers — CFDI issuance, materialidad evidence, withholding, and everything a studio needs beyond one person. Separating them out is deliberate: a feature map that blends intentions with shipped code reads as a larger product than exists. See what each tier costs →

Track the work

3 built

The question a freelancer opens the tool to answer: what am I owed, and what is due next.

  • Cash-flow dashboard

    Unpaid invoices, this month's earnings, and active project count — all derived from the data rather than stored, so the cards cannot contradict the table beneath them.

    SoloWeek 0open
  • Project & deadline table

    Client, financial value, days remaining, and one of four actionable statuses. Deadlines are computed against today rather than stored, so they never rot.

    SoloWeek 0open
  • Works without a database

    Every data path falls back rather than failing, and the page reports which path produced it. Not a feature anyone asks for, but the reason the product is demonstrable under failure.

    SoloWeek 0open

Get the work in

3 built

The failure mode of Week 0's product: a tracker nobody populates is worse than a spreadsheet, because the spreadsheet was already open.

  • Brief extraction

    Paste a client email and get a structured project: name, client, rate, hours, deadline, status, and a note saying what it was unsure about.

    SoloWeek 1open
  • Relative date resolution

    "End of next month" becomes a real date, resolved against today. Pattern matching cannot do this, which is why the module calls a model.

    SoloWeek 1open
  • Extraction provenance

    Every result states whether a model or pattern matching produced it, and that is stored on the saved row. Degradation announces itself instead of hiding.

    SoloWeek 1open

Know the market

3 built

Evidence the problem is real, and that no surveyed product solves both halves of it.

  • Competitor & substitute analysis

    Eleven products and substitutes with verified pricing, filterable by category and region. Zero of them do both project tracking and CFDI.

    SoloWeek 2open
  • Confidence on every claim

    Each factual row carries verified, reported, or estimated, and an unsourced claim renders visibly unsourced rather than passing as fact.

    SoloWeek 2open
  • Risk map

    Likelihood against impact, including the risks to this product's own thesis rather than only external threats.

    SoloWeek 2open

Price and plan

3 built

Turning the venture into tiers and a revenue model that can be argued with.

  • Three tiers, anchored to real competitors

    Each price is justified against a competitor figure fetched and dated, not chosen because it looked plausible.

    SoloWeek 3open
  • Revenue simulator

    MRR, ARR, blended ARPU, and a twelve-month projection that recompute live. Churn compounds and annual billing discounts properly — both are tested.

    SoloWeek 3open
  • Assumptions table

    Every input with its source, confidence, and what breaks if it is wrong. Most read estimated, which is the honest state of any revenue model.

    SoloWeek 3open

Invoice legally in Mexico

0 built · 3 planned

The gap the research found, and the reason the Pro tier can charge anything at all. None of this is built.

  • CFDI 4.0 issuance via a PACplanned

    Issue a legally valid electronic invoice through an authorized certification provider. This is the hard half and the actual differentiator.

    Pro
  • Materialidad evidenceplanned

    Link hours and deliverables to each invoice. The CFF reform effective January 2026 means an invoice must be backed by proof the work happened — and a CFDI tool that never saw the work cannot produce it.

    Pro
  • Withholding handlingplanned

    A company paying a RESICO freelancer withholds 1.25% ISR. The invoice and the cash received differ, and the dashboard should know that.

    Pro

Work as a studio

0 built · 3 planned

What Segment B needs beyond a single freelancer's view. Not built.

  • Multiple seatsplanned

    More than one person on one account, each with their own projects.

    Studio
  • Cross-person project viewplanned

    See every project across the studio, not one person at a time.

    Studio
  • Per-person profitabilityplanned

    Which work actually makes money once the hours are counted.

    Studio