The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Board — Enterprise Planning Platform Website Design (SaaS)
A high-trust, enterprise-grade website designed for Board, an Intelligent Planning platform used by 2,000+ global brands to unify financial and operational planning. The challenge was to communicate serious enterprise credibility while keeping the experience clean, modern, and easy to navigate for finance, supply chain, sales, and ops decision-makers.
The hero leads with a layered dashboard visual to instantly showcase product depth, paired with a bold headline and dual CTA strategy ("Request a Demo" / "Find your Solution") to serve both high-intent and exploratory visitors. A trusted-logo bar featuring recognizable enterprise brands reinforces credibility right above the fold.
Deeper down, the page uses a card-based solutions grid to break complex offerings (Finance, Supply Chain, Sales, Retail, Manufacturing, CPG) into scannable, benefit-led sections — each with its own CTA to keep momentum going. A dark-mode platform section highlights the product's core architecture with a custom circular diagram, while a metrics band (2000+ customers, 92% recommend, 75% reduction in planning time) builds quantifiable trust.
Social proof is layered throughout: enterprise case study quotes from Coca-Cola, DHL, and Toyota, analyst recognition badges (Gartner, IDC), and a global partner network section featuring Microsoft, KPMG, CGI, and EY. A resources/news module keeps the brand positioned as a category thought leader, and the page closes with a strong, focused conversion band driving toward a live product demo.
Every section was structured around one goal: move enterprise buyers confidently from "what is this" to "let's talk to sales" — without ever feeling like a hard sell.
Open to enterprise SaaS and B2B platform projects — let's talk about your next build.
Saas landing page
The dual-CTA split — "Request a Demo" for high-intent visitors vs. "Find your Solution" for browsers — respects funnel stage instead of forcing every enterprise buyer into one sales form regardless of readiness.
I appreciate it :)
Love the simplicity and strong design choices!
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
404 page interaction for the upcoming framer template
This is nice
One of the fintech products I worked on earlier this year.
I helped the team reshape the user experience, making the product easier to understand and navigate without adding unnecessary complexity.
I documented the thinking, decisions, and work in a case study.
Take a look and let me know what you think.
https://contra.com/p/7eYeXerB-swychr-rebuilding-a-global-payments-experience?referralExperimentNid=DEFAULT_REFERRAL_PROGRAM&referrerUsername=blissdezigns
Excellent work !
Hey! I just shared a write-up on something I learned while rebuilding a product with AI agents:)
The main idea is pretty simple:
Don’t put all your product context in one giant agent file.
Keep the main file small, and put the real product knowledge inside structured docs that the AI can navigate when it needs them.
This has helped me a lot when working on a SaaS product with a lot of business logic!
Sharing the full breakdown here:
I'm offering consulting services to set this up! :)
The table-of-contents-in-the-main-file pattern is the key move here - it keeps the agent's default context small while still giving it a map to go fetch the architecture or naming-convention doc only when the task actually touches that domain.