Understanding the problem
Background
- FileMaker Pro is a widely-used low-code platform with disjointed architecture and workflows
- Claris leadership prioritized AI to stay competitive and respond to disruption in the low-code space
- Product Owner (Ronnie) had gathered customer feedback and identified Calculations and Script Workspace as AI pilot areas
- Engineering built a quick MVP to test feasibility
Customer Feedback
- Customers liked the AI direction but wanted it embedded across the full development flow
- They criticized the disjointed app-building experience and praised Cursor’s centralized layout
- These customers closely aligned with our primary persona, Paula, reframing our strategy toward end-to-end AI support
Product Owner and I leading a stakeholder feedback session to evaluate the MVP direction and identify areas for improvement.
Problem Statement
- The MVP addressed isolated pain points, but the broader development workflow remained fragmented
- Customers struggled with modal overload and disconnected steps across the platform
- To make AI truly valuable, we needed to redesign the platform structure to support end-to-end intelligence