Giomar Maestre
ES / ENMenu
DOCUMENTED CASE · VERIFIED EVIDENCE

Case study · Business Intelligence

PilotOrb: turning QuickBooks data into clear business decisions.

PilotOrb needed to turn billing, customer, and product data into a visual experience that leadership, sales, and marketing teams could understand. I collaborated with the founders on the initial definition and design of a Business Intelligence platform integrated with QuickBooks Online.

MY ROLE

Product Designer — Business Intelligence & Data Visualization (Consultant)

Discovery · Information architecture · Data visualization · Wireframes · Figma/FigJam prototyping

Turning accounting data into a business story

The challenge was not to surface more data, but to help non-technical teams understand business behavior without relying on traditional accounting reports. That required defining what question each screen needed to answer before designing a single chart.

My responsibility

I worked directly with the founders to translate their vision and data requirements into a coherent experience proposal: user profiles, information architecture, the main dashboard, exploration filters, and interactive prototypes. My contribution was concentrated in the initial definition and design stage; I was not involved in implementation or later product phases.

From scattered accounting data to an explorable dashboard

  1. Start from business questions, not tablesI defined the priority analysis scenarios with the founders (sales trends, customer behavior, inactive products) before designing any visualization.
  2. Design a single entry dashboardThe Home dashboard concentrates overall metrics, a weekly overview, and recent highlights, so any user understands the state of the business in a single view.
  3. Make data explorable, not just visibleI designed filters by customer, product, period, and geographic location that move from a general view to a specific analysis without switching screens.
  4. Compare, not just reportI introduced a neighboring-analysis concept (comparable periods) so trends read in context rather than as isolated figures.
  5. Document decisions for the next teamI organized research, requirements, and product decisions in Notion, with interactive prototypes in Figma/FigJam, to leave a clear foundation for implementation.

Real evidence authorized by the project's founders

PilotOrb's founders authorized reproducing screens from the final design developed during the engagement in this portfolio. The screens are taken directly from the project's Figma design files; they are not screenshots of a production product and include no real customer data.

Product identity

P-B1 · 01/6 PilotOrb logo

PilotOrb logo: a blue circular icon with a center dot and the words PILOT ORB in a technical typeface.

Product: Business Intelligence platform

P-P1 · 02/6 Sign in

PilotOrb sign-in screen with an email and password form over a blue-toned office photograph.

P-P2 · 03/6 Home dashboard

PilotOrb Home Dashboard with overall metrics, a recent weekly overview, and inactive-product highlights.
Explore additional evidenceHide additional evidence

Product: Business Intelligence platform

P-P3 · 04/6 Your Sales — sales analytics

Your Sales dashboard with yearly trends, quarterly neighboring analysis, and top-customer and top-product tables.

P-P4 · 05/6 Product Explorer

Product Explorer showing a single product's summary, its unit-sales trend, and customer performance.

P-P5 · 06/6 Project Manager — account and project

Project Manager screen with project preferences, subscription status, and the project's user list.
5 months
of discovery and initial design
6 screens
of authorized real evidence
QuickBooks Online
as the integrated data source
Figma + FigJam
for prototypes and research

An experience and architecture foundation for a Business Intelligence product

The engagement established the experience and information-architecture foundation for turning QuickBooks Online data into useful planning insights. The value of the case lies in the clarity of the product reasoning, not in adoption metrics or business outcomes that were not measured during my involvement.

Declared limitations

No real financial data or adoption metrics are published. This case does not claim the product was implemented in production or that it continues to operate with this design; my involvement was limited to the initial definition and design stage (Jul.–Nov. 2023).

About this evidence

PilotOrb was an early-definition engagement, not a public product with a verifiable reference site. For that reason, this case does not link to an external website.

Design work completed during a professional engagement with PilotOrb's founders, who authorized reproducing the final design screens developed during the project in this portfolio. PilotOrb never reached public production, so this evidence comes from the project's Figma design files, not a live product.