Guide

How Fygurs works, screen by screen, in the order you meet it. Every chapter says what the screen shows, what you can do, and the rules that hold.

Updated on 13 October 2026

  1. 1.Getting startedA workspace is created in one step. You name your products, then choose where to start: your list, your bets or a diagnostic. Everything can be changed later.
  2. 2.The home pageThe home page reads in ten seconds: what the workspace holds, what waits on someone within fifteen days, where the bets stand, and what moved in the last thirty days.
  3. 3.InitiativesThe initiative is the central object: a list you browse from the keyboard, a one-line creation, and a page that carries everything a committee asks for.
  4. 4.The matrix, the roadmaps, the mapThe same initiatives, read differently: by value and feasibility, over time, by stage, or linked to their bets and products.
  5. 5.Products and portfoliosA product carries initiatives. A portfolio groups products. It is the backbone of the map, of the list's groups and of programme committees.
  6. 6.BetsA bet says why you run these initiatives, in one sentence a committee understands. Three to five at a time, with a metric, readings, and a date to decide.
  7. 7.ScoringA value and a feasibility out of 100, scored criterion by criterion on written rungs, a size and a confidence. The priority score ranks the list.
  8. 8.The business case and the observed gainCost and gain lines on the initiative, a break-even, a validation by a committee decision, then readings at 30, 90 and 365 days up to the observed gain. A figure is worth what its proof is worth.
  9. 9.CommitteesA committee has a cadence and a pack. A session is prepared from today's data, presented full screen, and what gets decided is written on the bets and the initiatives.
  10. 10.The maturity diagnosticA few questions in conversation give a score out of 100, a stage, a profile by category, then three bets and a first portfolio, with figures drawn from your answers.
  11. 11.GitHubA read-only link. Fygurs reads the milestones and issues of the repositories you name; a milestone attached to an initiative gives it its real progress and its real date, next to the planned one.
  12. 12.The use case libraryTwenty AI use cases, each with the question to ask, the metric to read and orders of magnitude taken from open studies, never from vendors. The fiche brings the question and the measure. Your company brings its own numbers.
  13. 13.Import a roadmapA spreadsheet, a deck or a PDF. Each row is read, then you check what becomes what before anything is saved. A second import of the same file updates without creating duplicates.
  14. 14.Team, settings and planWho is in the workspace and what each person may do, your profile and preferences, the workspace's identity, the plan and the invoices.