Qompyl
Lead Product Designer
Apr – May 2026
Investor-Ready in
4 weeks. Not 4 months.
How I redesigned Qompyl's digital presence ahead of investor outreach and market launch — balancing trader clarity, company credibility and protection of proprietary product concepts on an aggressive timeline.
Qompyl was preparing for investor outreach and a broader market introduction, but its existing website no longer reflected the sophistication of the product or the company behind it. The team needed a significantly stronger digital presence — and needed it in approximately four weeks.
Trader-first, investor-reassuring. The site used layered content, simplified product storytelling, selective product visuals and a credibility-first hierarchy to serve prospective users, investors and partners without overexposing proprietary concepts.
A five-page Webflow site launched on schedule, giving Qompyl a polished public presence aligned with investor outreach, social launch and early-access acquisition. Investor feedback specifically commented on the site's polish during due diligence.
The brief, the baseline
The first-impression challenge
Qompyl needed to answer several questions almost immediately: What does the company do? Who is behind it? Does the product feel credible and differentiated? And is there enough here to warrant a deeper conversation?
Everything else — the visual system, copy hierarchy, product storytelling and interaction design — supported those first-impression goals.
- • Juggling multiple disconnected tools
- • Limited access to sophisticated strategy-building and testing workflows
- • Difficulty translating trading ideas into repeatable rules
- • A more unified trading workflow
- • Backtesting and strategy-building capabilities
- • Greater structure and consistency in execution
Investors and advisors approaching Qompyl needed to quickly understand the company, product proposition, team and market ambition without having to navigate highly technical product detail.
- • Clear company positioning
- • Credible leadership and team presentation
- • Understandable product differentiation
- • Evidence of product maturity
- • A clear path to deeper engagement
The client
- Qompyl's public presence needed to catch up with the sophistication of the product and the ambitions of the company.
- Investor outreach raised the standard for credibility, clarity and polish.
- The website also needed to support Qompyl's broader market introduction, social launch and early-access acquisition efforts.
- Because the product was still evolving, the team needed to communicate its value without overexposing proprietary product concepts.
The challenge
"We needed the website to reflect the sophistication of what we were building while making the product understandable to prospective users and credible to investors — without revealing more of the product than we were ready to share publicly."
Core pain points
- 01Credibility gap — the old site didn't reflect the sophistication of the product or the company behind it.
- 02Multiple audiences — prospective traders, investors and partners arrived with different questions. The content hierarchy needed to serve all three without becoming diluted or overly technical.
- 03Product/IP sensitivity — Qompyl needed to demonstrate how the product worked and why it was differentiated while remaining selective about what aspects of its underlying logic and architecture were shown publicly.
The opportunity
Qompyl needed to avoid two common extremes: a technically dense presentation that overwhelmed prospective users, and a generic SaaS presentation that failed to communicate the sophistication of the product.
The opportunity was to create a site that felt credible, modern and understandable from the first interaction.
The 4-week sprint
Five overlapping stages across approximately four weeks.
Alignment & de-risking
Strategic brief, audience alignment and IP guardrails.
Architecture & flow
Low- and mid-fidelity wireframes across all five pages.
Trust-building UI
Visual design and component system.
Scalable Webflow build
Responsive build, CMS and QA.
Analytics & launch
GA4, Microsoft Clarity, testing and launch.
Research, stakeholder alignment, audience priorities, IP guardrails and low-fidelity wireframes.
Mid-fidelity to high-fidelity design and visual system development.
Webflow build, responsive implementation and CMS setup.
Analytics, UAT, revisions and launch.
Three principles that shaped the direction
These principles guided every design decision from kickoff to launch.
Credibility has to be immediate
Visitors should not have to dig through the site to understand what Qompyl is or whether the company is serious.
Design response
Hero positioning, team presence and product depth surfaced above the fold — credibility signals visible without a single scroll.
Complexity needs progressive disclosure
The product is sophisticated, but the first interaction should not require understanding the entire system.
Design response
Layered content, simplified product explanations and deeper information for visitors who wanted it.
Measurement needed to start at launch
The redesign needed a feedback loop once real visitors began interacting with it.
Design response
GA4 and Microsoft Clarity incorporated at launch.
The strategy
Trader-first, investor-reassuring — built around a deliberately layered audience hierarchy.
The content hierarchy was intentionally designed so a time-constrained visitor could understand the company at a high level before choosing where to go deeper.
IP protection
Public-facing visuals focused on user-facing inputs, workflows and outcomes rather than detailed representations of proprietary product architecture.
V1 vs. Vision separation
Available capabilities and future roadmap items were visually differentiated so Qompyl could communicate product ambition without blurring what was live versus still in development.
Trader-first language
Complex product concepts were translated into clear, accessible language focused on what the trader could do rather than how the underlying system was built.
Why this strategy?
- Investors and traders read the same page differently. The hierarchy needed to work for both.
- The design had to communicate sophistication without unnecessary technical exposure.
- Roadmap items needed to create anticipation without implying they were already available.
Built to scale
Not pages — a system the team can run, extend, and hand off to any developer without me in the room.
Design tokens
A reusable visual system helped keep color, typography and spacing consistent across the site.
Components
Reusable components made future page creation and content updates faster and more consistent.
Accessibility considerations
Contrast, semantic structure, accessible labeling and keyboard usability were considered throughout the build.
CMS
Team, blog and other repeatable content types were structured for easier self-service updates.
From wireframe to launch-ready
Low-fi structure to pixel-perfect system — across all five pages.
Low-fidelity wireframes
StructureGrayscale layouts focused on hierarchy and core functionality — no visual design yet.
.png&w=1536&q=80)
.jpg&w=1536&q=80)
.jpg&w=1536&q=80)
Mid-fidelity wireframes
RefinementReal copy and clearer hierarchy — the bridge between structure and visual design.
.png&w=1536&q=80)
.jpg&w=1536&q=80)
.jpg&w=1536&q=80)
Color System
Typography
Spacing scale
Radius scale
High-fidelity UI
Final designPixel-perfect visual design across all 5 pages — premium fintech aesthetic, fully responsive.
.png&w=1536&q=80)
.jpg&w=1536&q=80)
.jpg&w=1536&q=80)
Post-launch receipts
Launch wasn't the finish line. It was the starting gun. Here's what the tracking stack reported in the first 30 days.
Recordings didn't show where the site failed. They showed where trust had already been earned. Visitors clicked into team bios, explored job listings, searched for security details and went deeper into the company.
The placeholders they found, the incomplete destinations and the links that stopped them weren't failures of the design system — they were content and implementation gaps that surfaced after launch. The site built the trust. The team just had to fill the room.
Impact & results
Four measurements. Four different truths — speed, quality, returning engagement, and depth.
Sources: All metrics verified via Microsoft Clarity (30-day window post-launch). Returning visitors = 169 of 634 sessions · Pages per session = median, not mean · Revision rounds = Figma file history.
Investor feedback
Investor feedback specifically commented on the site's polish during due diligence — a meaningful indication that Qompyl's external presentation was aligning more closely with the seriousness of the company and product.
"Mamdouh brought much more than design expertise to our project. He took the time to understand our business, product and team, helped us identify what we were missing, and guided us through how to tell our story more effectively. When challenges arose, he consistently came back with thoughtful options and helped us work toward the best outcome. He was professional, responsive, collaborative and an absolute pleasure to work with — and I would work with him again and again."
What I'd do differently next time
A case study without confessions is an advertisement. Three things I'd change if I started this project tomorrow.
What I'd do differently
- 01Ship content before design. Clarity recordings caught visitors clicking into empty "Coming soon" placeholders. The design earned their curiosity — the copy wasn't ready to answer it. Next time: final copy locked before the first wireframe.
- 02Test stability at mid-fi, not at launch. Post-launch recordings flagged recurring JS errors on the Team pages. The fix was 20 minutes. The discovery took 20 days. Next time: error monitoring wired into the first staging build.
- 03Audit mobile conversion earlier. Most traffic arrived on a phone. Most signups came from desktop. That gap existed for weeks before it was flagged. Next time: mobile funnel instrumented from day one — not retrofitted at week four.
Next steps
"A four-week deadline doesn't buy perfection. It buys clarity about what to fix next."
This isn't another fintech website.
It's proof that clarity can outpace complexity — even on a four-week clock.
Reply within 24 hours. Usually sooner.