Entering the Base44 Challenge with Brief to Quote.
I design technical documents, and every project starts with a brief that's missing something. So I built a small app: the client answers a few questions, gets an instant estimate and a tracking code, and I see every request in a dashboard.
Would love feedback from other builders: what would you add?
The first thing I created for LedgerFlow wasn't a screen.
It was a set of questions.
I'm kicking off a new concept project: **LedgerFlow, an accounting and financial management SaaS platform for small businesses, freelancers and independent business owners.
The goal is to design a website that helps visitors understand what the product does, how it helps their business, and why they should book a demo.
But before opening Figma, I needed to understand the business.
So I created a website discovery and brand strategy questionnaire.
It covers:
→ Brand vision and business goals.
→ Target audience.
→ Website goals and user experience.
→ Branding and visual direction.
→ Services and offers.
→ Project direction and logistics.
I want to understand things like:
Who exactly are we designing for?
What problem does the product solve?
What makes it different from traditional accounting software?
What should visitors understand within the first few seconds?
And what would make them confident enough to book a demo?
Because the answers will influence the website's messaging, content, visual hierarchy and calls to action.
You can't design a clear experience when you don't understand what the business needs to communicate.
LedgerFlow is a concept project, but I'm treating the process like a real client engagement.
I'll be sharing the journey from discovery to website structure, UI design and Webflow development.
And if you're building a SaaS product or need a website that communicates your business value clearly, I'm open to website design and Webflow projects.
Starting with a discovery questionnaire instead of a screen is how good briefs begin, and "explain what LedgerFlow does in the first seconds" is the right goal to design around. Will the answers become a one page brief?
A status label alone doesn't explain what happens next.
In this Strata practice project, the request screen combines the resident's conversation with the building manager, its current status, and a progress timeline.
A useful UX check is to ask which updates customers still have to call for. If the answer is already in the system, make it visible to them.
Which update would you put on screen first?
Practice UX/UI project for a fictional company. Sample data.