AssetFixMe

What the company appears to be: AssetFixMe is a self-reported, single-developer project built with Flutter and Firebase, designed to help teams report, assign, track, and complete maintenance requests for assets. The author states that AI (ChatGPT and Codex) was used as a development partner but not inside the application itself.

What changed: The author reports building the product from almost no coding experience over about one year, using AI tools to learn and develop. The project is described as having evolved from an idea into a multi-platform app with features like QR reporting, media uploads, notifications, and service history tracking.

The single most important open question: Is there any evidence of actual user adoption or business traction beyond the author's own development experience?

• The description states that AssetFixMe is a system for teams to report, assign, track, and complete maintenance requests.
• A problem can be reported with photo, video, description, or QR code.
• Managers assign requests to technicians; technicians complete repairs.
• Full history stays connected to the asset.
• Built using Flutter and Firebase.
• The author states that AI was used for development but not inside the application.

Evidence strength: Self-reported. No independent verification of product functionality or user adoption.

• The author claims the project started as a proof-of-concept to show that non-developers can build real products with AI assistance.
• The positioning evolved from "learning to code" to a functional asset management tool.
• The author states they are proud of moving from "almost no coding experience" to publishing a multi-platform product.
• No evidence of market positioning or messaging beyond the author's own account.

Evidence strength: Self-reported. No evidence of customer feedback, market testing, or competitive positioning.

• The description states that AssetFixMe is designed for hotels, property management, workshops, marinas, offices, small businesses, and homes.
• The author describes the product as useful for "teams" and "asset management."
• No evidence of specific customer segments or personas beyond general categories.

Evidence strength: Self-reported. No evidence of actual customers or target market validation.

• The description does not state any pricing model, monetization strategy, or business model.
• No mention of subscriptions, usage fees, or revenue streams.
• The author states that AI was used for development but not inside the app.

Evidence strength: Not evidenced. No information on how the product would generate revenue.

• Built with Flutter and Firebase.
• Uses authentication, user roles, permissions, Firebase security rules, notifications, media uploads, QR codes, request workflows, and publishing for Android, iOS, and web.
• The author reports using ChatGPT to understand programming, plan features, solve problems, and write code.
• Codex is now used for improving features and fixing issues faster.
• No evidence of product maturity or technical scalability.

Evidence strength: Self-reported. No independent verification of technical delivery or performance.

• The author reports building the product in about one year from almost no coding experience.
• The app is described as having evolved to include asset management, maintenance requests, roles, QR reporting, photos, videos, notifications, service history, periodic maintenance, and handover workflows.
• No evidence of user adoption, customer base, or revenue.
• No mention of product usage metrics, retention, or growth.

Evidence strength: Self-reported. No evidence of traction or business maturity.

• The description does not mention any competitors or market context.
• No information on existing solutions in the asset management or maintenance tracking space.
• No evidence of competitive differentiation or positioning.

Evidence strength: Not evidenced. No competitive analysis or market data provided.

• The product is described as a single-developer project with no evidence of team, funding, or external support.
• No revenue, customer base, or traction data.
• AI was used for development but not inside the application — this may limit scalability or differentiation.
• The author reports challenges in learning software development while building the app, suggesting potential technical limitations.

Evidence strength: Inferred from self-reported description. No independent validation of risks.

1. What is the actual user base or adoption rate for AssetFixMe?
2. How does the product plan to monetize or generate revenue?
3. Are there any existing competitors in this space, and how does AssetFixMe differentiate?
4. What are the technical limitations or scalability concerns of the current architecture?
5. Has the author tested the product with actual users from the target industries (e.g., hotels, workshops)?
6. How is the product currently being used beyond the developer’s own experience?

Evidence strength: Inferred from self-reported description. No independent data to support these questions.