Retrace Enterprises ยท Product Roadmaps

Product Roadmaps

A coordinated development roadmap for the Retrace product ecosystem, designed to prioritise stability, revenue impact and customer value before expanding into additional applications.

Core active products3
Near-term focusStability
Expansion ruleValidate first
Review cadenceQuarterly

Portfolio Roadmap

Development sequence based on commercial role and readiness.

Focus before expansion
Portfolio Roadmap
ProductCurrent RoleNext MilestoneSuccess GatePriority
ArmariumFlagship revenue productPolish onboarding, licensing, import/export and Structured ViewStable release, strong conversion, low refund rateHighest
BulkHound ProSearch-driven utilityComplete safe scanning, protected-file handling, exports and differential analysisAccurate results, safe deletion, reliable large-drive performanceHighest
StoneAccessible mobile creator productStabilise recording, autosave, offline use and noise handlingReliable mobile sessions and three daily salesHigh
SeekHawkFuture professional search toolValidate core search-and-replace workflowClear professional demand and premium pricing caseMedium
FoundryFuture productivity platformPrototype idea-to-specification workflowDistinct use case and manageable scopeMedium
Ecosystem AuditorHigher-value business toolValidate forensic hosting audit reportsAgency/business willingness to payMedium

Quarterly Delivery Plan

Roadmap priorities across the operating year.

Q1

Stability

  • Complete release gates.
  • Fix critical workflows.
  • Standardise installers.
  • Finish support documentation.
Q2

Conversion

  • Improve onboarding.
  • Refine pricing pages.
  • Ship high-value usability fixes.
  • Measure support friction.
Q3

Expansion Validation

  • Prototype one professional tool.
  • Test demand before full build.
  • Introduce bundle concepts.
  • Review upgrade opportunities.
Q4

Consolidation

  • Strengthen proven products.
  • Retire weak features.
  • Approve Year 2 roadmap.
  • Document technical debt.

Roadmap Decision Rules

Rules for keeping development commercially disciplined.

Build

Only after validation

New products move into full development only when the user problem, audience and pricing case are clear.

Pause

Stop low-value work

Pause features that add complexity without improving sales, safety, retention or customer value.

Finish

Complete before multiplying

Do not open too many active product fronts while core products remain unstable or under-supported.

Each roadmap item should have an owner, acceptance criteria, release target and measurable business reason.