About Loonar
Loonar helps industrial engineering teams (valves, pumps, energy/process equipment) turn massive technical and commercial specification documents (hundreds to thousands of pages per RFQ) into structured, actionable answers: what the customer is asking for, what we can offer, what we can't.
Every extracted data point traces back to its source paragraph, this auditability is core to the product and to user trust. The product is five months old, has ~100-120 users, and is built by a small team without a formal design system.
The problem
Our users are technical/commercial engineers at traditional industrial companies, not digital natives, but they need the product to be extremely intuitive.
Today it works, but outputs are dense walls of text and the interface has grown organically without UX rigor. We need to cut information overload and make a genuinely complex workflow feel obvious.
Scope of this engagement
Trial: one paid pilot week, working hands-on with us to redesign one of Loonar's five core pages. We decide together whether to continue after that.
If it continues: iteratively revisit the five main pages, one at a time, identifying friction points and redesigning for clarity before pages go back into production.
What we need
Not a static design system delivered up front. The product will keep changing fast, we need durable UX principles and reusable patterns we can build on, not a Figma snapshot that's outdated on day one.
Someone comfortable working close to the codebase (Claude Code / component-level), not necessarily Figma-first, we have no existing design files.
A minimalist, opinionated eye: what to show first, what to progressively disclose, how to make dense technical output scannable without hiding the traceability to source documents.
Judgment on lean, reusable components over one-off, over-componentized screens.
Ideal profile
Product designer with UX research instincts and a technical/engineering background, someone who can sit between product and engineering, understand a complex domain quickly, and turn that understanding into interface decisions, not just visuals.