Masum transformed our data-heavy product into a clean, intuitive experience. His design decisions were thoughtful, efficient, and optimized for constrained layouts. Highly recommended.

Richard Jackson
CEO & Co-Founder, Alphaletz.com



Gantt
Who uses it and whyConstruction managers open the Gantt every morning to find which tasks need fixing or start today, then check owners, dates and progress across all their projects.
3 versions
AI observationThe schedule had all the information, but managers had to work too hard to use it. Every project was its own full Gantt with its own tabs, column header and calendar, so a manager read three near-identical charts before making a single decision. Overdue work and impossible dates were hidden inside coloured bars, and nothing said what starts today.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. On this page, lead with the exceptions. Put what needs attention and what starts today above the chart, and write each problem in words on the task row instead of leaving it inside a bar.
What the AI changedStarts today and Needs attention now open the page. Problems are written on the row in plain words, like Overdue or Invalid dates, and today is marked in the calendar. Each project became a collapsible block with its deadline and completion in the header.
AI observationThis was real progress. A manager could see the morning's decisions before touching the chart. But the page was still a stack of separate containers: two summary boxes, then one rounded box per project, each repeating the whole calendar header. Planning across projects still meant re-reading dates. The next step was one shared planning workspace where every project lives on the same calendar.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Turn Needs attention and Starts today into flat lists, with Needs attention first and a Fix dates link on each problem row. Use one shared Gantt sheet with the calendar header shown once, and make each project a slim band inside it. Apply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed.
What the AI changedThe summary boxes became flat lists, with Needs attention first and Fix dates beside each problem. All projects now share one sheet and one calendar header, with each project as a band carrying its own deadline and tools. Projects › Gantt became a breadcrumb, and Timeline and Calendar moved into the sidebar as sub-items.
AI observationNow the page follows a manager's actual morning: fix what is broken, see what starts today, then plan. Because the dates are said once, the eye moves from one project to the next without re-reading headers and compares work across projects on the same dates. The page is organised around the decisions a manager makes, not just the data the system holds.
Rule to take with youDesign a schedule around the decisions people make with it. Problems first, and one shared calendar instead of one per project.



Paymie
Who uses it and whyFinance and operations leads use this page to check how the payment business did over a period: total volume, earnings, where the money comes from, and which merchants drove it.
3 versions
AI observationThe data was all here, but every block spoke at the same volume. Six KPIs, a currency list with icon chips, a world map with a flag legend and a merchant table all competed for attention, and the map repeated what the country list already said. A finance lead had to piece together the story of the period on their own.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep Paymie. Lead with the period numbers in one strip, then show where earnings come from, then which merchants drove volume.
What the AI changedThe page gained a reading order: a KPI strip at the top, currency and country lists with share bars, and a merchant table below.
AI observationThis version finally read like a money page, top to bottom. What held it back was the split into three rounded cards with a decorative map sitting above the country list, so the story broke at every card edge and one answer was given twice. The next step was one money surface where the whole period reads as a single connected answer.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Merge the three cards into one white panel divided by thin lines. Make the KPI strip six divided cells. Put inline bars on the currency and country rows, and remove the world map because it repeats the country table. Rank merchants by share of volume. Keep the logo and the header controls exactly as they are in this version.
What the AI changedThree cards became one white panel split by hairlines. The KPIs sit in six divided cells, currency and country rows carry inline bars, the world map is gone, and merchants are ranked by share of volume. The sidebar active state became a soft grey instead of a white pill.
AI observationNow the page makes one clear statement about the period. The numbers lead, earnings by currency and volume by country sit side by side and compare at a glance, and the biggest merchant is row one. Because nothing is said twice, each block answers a different question, and a lead can explain the month in one read.
Rule to take with youIf two visuals answer the same question, keep the one people can compare and rank. Removing the map made room for the answer.



Payper · customer details
Who uses it and whySupport and finance teams open one customer to check how much went through, what failed, and the customer's contact facts, often while that customer is waiting on the line.
3 versions
Masum's thoughtThe customer's identity and technical details took as much room as the payment activity people actually come here for. Rare actions belong in a ⋯ menu. Identity should be a compact header, not a big left panel. The device and IP list can go, because the user is not here for it. And the chart should be Stripe-simple: one series, one line.
To the AIKeep the Payper product. Put identity in a compact header, keep a simple one-series chart, move rare actions into a menu, and avoid nested cards. When an early pass came back as a grid of rounded floating cards, I sent it back: "you followed codex design, I wanted to see your design".
What the AI changedThe page now opens with an approved-spend chart drawn as one line, identity and key facts beside it, and a transactions table filtered by All, Approved, Pending and Declined.
AI observationThis got the order of the job right. A support person can answer "what happened with this customer" from one screen. It still leaned on boxes, including a grey box nested inside the facts card, so the supporting facts felt as heavy as the activity itself. The next version needed the work area to clearly lead and the facts to clearly support.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Remove the cards: soft stone sidebar, white work area, sections split by thin lines. Keep the compact identity header and show the facts as an open, secondary panel beside the chart. Draw the chart as a clean line with a dashed previous period, aligned to the first and last dates so it never looks cropped. Flatten the payments table and use small status tags without strokes. Keep the current logo.
What the AI changedAll cards were removed. The identity header stays compact, the facts became an open panel beside the chart, and the chart is a single green line with a dashed previous period aligned to its date edges. The payments table is flat, with small 4px status tags.
AI observationNow the page is ordered like a live support call. Who the customer is takes one line, the spend trend and the facts share a row, and the payments run underneath, so "which payment failed" is answered by scanning down. With no nested boxes, the activity leads and the facts quietly support it.
Rule to take with youGive each part of a page the weight of its job. Activity is why people come; identity and facts are there to support it.



Paymie V2
Who uses it and whyThe same payments team uses this report view to read a period's results, see merchant contribution, and export or edit the report without leaving Paymie.
3 versions
AI observationThis report reused the overview's widget mix: an icon-chip currency list, a world map with a flag legend, and a merchant table. For a page people export and share, nothing signalled which results mattered, and the decorative map took space away from the numbers.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep the same product look as the Paymie overview, so report mode feels like the same tool.
What the AI changedThe report became readable, with summary blocks at the top, a country bar for volume, and clear merchant rows below.
AI observationThis version did the basic job well, and the numbers were easy to find. But separate summary cards and a multi-colour country bar made report mode louder than the overview it belongs to. Someone moving between the two would feel they had switched products. The direction was simple: the same product, just quieter.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Use the same shell as the overview with four KPI cells. Turn the summary cards into divided cells. Remove the multi-colour country bar and keep one accent colour. Add a rank column, show a real fourth merchant so Top 4 is true, and make the footer share total match the rows. Keep the current logo and avatar controls.
What the AI changedThe report now shares the overview's shell. Four KPI cells replace the summary cards, the multi-colour bar is gone, merchants have a rank column, a fourth merchant makes Top 4 honest, and the footer share total reconciles with the rows.
AI observationNow it feels like the overview in report mode. Four numbers open the page, merchants are ranked with a total that adds up, and one accent colour carries the data. An exported report reads as a clean document someone can trust, and nobody has to relearn where things are when switching views.
Rule to take with youA report view should feel like the same product in a quieter voice, and every total on it should add up.



Payper · customer details V2
Who uses it and whyOps and support teams use this view to scan a customer's recent transactions and spend while keeping the customer's facts at hand.
3 versions
Masum's thoughtThis page had the same problem as the first customer page: identity and technical facts were as loud as the activity. My Payper direction stayed the same here. Compact identity, a one-series chart, and no floating-card grid.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep the same Payper shell as the first customer details page so both screens feel like one product.
What the AI changedThe chart, a compact customer card and a filtered transactions table now share one page, matching the first customer details screen.
Masum's thoughtThis version brought the two customer screens together, and that consistency mattered. My concern for the next pass was space. The table could use the full width. Why leave empty space beside it for no reason, when people come here to read transactions?
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Use a work column plus a customer rail, but only beside the chart. Let the transactions table run the full width underneath. Remove the nested grey boxes. Show status as a dot and a word instead of a pill, use clean tabs for the status filter, and make the pager match the real transaction count. Keep the current logo.
What the AI changedThe customer rail now sits only beside the chart, and the transactions table runs full width below it. Nested grey boxes are gone, status reads as a dot and a word, the filter uses clean tabs, and the pager matches the 26 real transactions.
AI observationNow the table gets the room it needs, so more transactions are visible without scrolling. Dot-and-word status keeps a long list calm, and the pager tells the truth. Because it matches the first customer page in shell and density, the two screens feel like one tool.
Rule to take with youWidth belongs to the content people scan most. A side rail should only sit where it earns its space.



BRICK · timeline
Who uses it and whySuperintendents and project managers use the timeline to see what each crew is doing today and over the next days, and what needs fixing.
3 versions
AI observationEvery part of this board was its own box: the summary, a card per project, and a small card per task in every day column. Today was hard to find across projects, and a rotated Estimate approved rubber stamp plus a round To be completed stamp competed with the schedule itself. A superintendent looking for "who is where today" had to read around the decoration.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep the BRICK identity and put the problems first.
What the AI changedThe board was tidied into the shared BRICK shell. Starts today and Needs attention lead with clear reasons, like Overdue or Invalid dates, each project has a clean header with completion and deadline, and the More info details sit behind a simple switch.
AI observationThis version kept the structure crews rely on and made the exceptions much clearer. The weak spot was still today: it did not stand out across projects, and the rubber stamp and boxed tasks kept pulling the eye away from the work. The next version needed today to be unmistakable and the schedule to be the loudest thing on the page.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Put Needs attention and Starts today flat at the top. Split the day columns with thin lines and show tasks as entries, not boxed cards. Tint today's column. Replace the rubber stamp with a quiet Estimate approved tag, and show free time as a small "+ 5 hours open" action.
What the AI changedExceptions sit flat at the top. Day columns are split by hairlines, today is tinted across every project, tasks read as entries, the stamp became a quiet Estimate approved tag, and open time became a "+ 5 hours open" action.
AI observationNow the board answers "what is happening today" first. Exceptions lead, today runs as one tinted column through every project, and each day reads as a list of tasks with crew, time and notes. Open time stopped being an empty gap and became something a manager can fill.
Rule to take with youOn a field schedule, today is the anchor. Make it visible across every project, and turn empty time into an action.



MonRize · merchants
Who uses it and whyPayments ops leads use this page to check merchant payment health for a period: volume, clearing rate, who drives volume, and what is about to be paid out.
3 versions
Masum's thoughtThe earlier live redesign was still too close to the original page, where every KPI and chart had its own period dropdown. I did not like the new-merchants bar chart, or the bottom row where merchant status, top merchants and upcoming payouts sat as separate panels. One Stripe-style date filter should drive the whole page, and Needs attention belongs in the bell.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep MonRize's own corner identity. Use one Stripe-style period filter for the whole page and move Needs attention into the bell.
What the AI changedOne period filter with a comparison now drives the page. Processed volume leads with its chart and money breakdown, payments cleared shows its failure reasons, merchants are ranked, and Needs attention moved into the bell.
AI observationThis version fixed the biggest problem: everyone now knows which period they are looking at, and volume, clearing and ranked merchants tell a clear health story. It was still five separate cards, though, so the page felt like a set of executive reports instead of one decision. The next step was one panel.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Merge the five cards into one square panel with corner notches and thin dividers. Let the period filter drive every number. Rank merchants and drop their logos. Make Merchants receive reconcile to volume minus revenue. Keep the current MonRize mark, and make sure the chart line ends clear of the plot edge.
What the AI changedFive cards became one square panel with corner notches and hairline dividers. The period filter owns every number, merchants are ranked without logos, and Merchants receive now reconciles to volume minus revenue.
AI observationNow it is one decision surface. The period is set once, volume and clearing read together, merchants are ranked by what they drive, and payouts follow as the next check. The sharp corners keep MonRize's character, while the single panel removes the feeling of five separate reports.
Rule to take with youLet one period control own the whole page. If every widget has its own filter, nobody knows what they are looking at.



BRICK · customer profile
Who uses it and whyAccount managers and office staff use this page to see what a customer owes or has not signed, then act on each document.
3 versions
AI observationThis page read like a filing cabinet. Totals were abbreviated figures with status counts, every document in the table had the same weight, and a long contact rail sat beside it. Nothing told the office person which document needed them first, or what to do about it.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Reuse the BRICK components 1:1. The documents that need action are the job, and contact facts support the job.
What the AI changedFull money figures for estimates, change orders and invoices now sit at the top. Documents are sorted with action first, and each row shows its status, how long it has waited and a next step such as Send reminder.
Masum's thoughtThis turned the profile into a work page, which is what it should be. As we refined it, I pushed hard on how it scans. The three money cards were not equal and felt unbalanced. The row menu and the Send reminder buttons did not share one alignment, and Value, Balance and Status were all misaligned. Two lines where the rail meets the sheet were useless.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Make the action documents the only white sheet. Show totals as a flat strip with equal-width money cells. Keep contact, notes and account details in an open rail. Right-align money columns, and put the row menu and the primary action on one vertical edge. Remove the orphan lines, and select People in the sidebar.
What the AI changedThe action documents became the only white sheet. Totals sit in a flat strip of equal cells, contact and notes moved to an open rail, money columns right-align, and every row ends in one aligned next step. People is now the selected sidebar item.
AI observationNow the follow-up call is easy to start. The totals strip says what is owed in one line, and the only white surface is the list of documents that need action, each with one clear next step on the right. Contact details sit open beside it for when the person needs to phone or email.
Rule to take with youA customer profile is a to-do list about one person. Lead with what they owe or need to sign, and give each row one next step.



BRICK · time log details
Who uses it and whyPayroll admins use this page at the end of a closed pay period to decide whether payroll can run, and what is blocking it.
3 versions
Masum's thoughtWhy do we have only one tab here, Worked details? How is this page functional? Check the old version in the history first. The lower tabs were very strong and needed to be softer. An earlier redesign was simply wrong: it dropped Convert to overtime, the pay period arrows, Total paid and the pay rate, and its numbers did not add up.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Study the old version and every state first. Rebuild around the payroll decision, keep every action and every piece of content, and follow the UX guides. Move Time logs under Time tracking as sidebar sub-items with a breadcrumb. Replace the two arrows with one Shopify-style period picker, and keep every label and number on one consistent alignment.
What the AI changedThe page was rebuilt around the payroll decision. Time tracking › Time logs is the breadcrumb, one period chip replaces the arrows, and Left to approve leads the summary. Each worker shows what needs attention, Convert to overtime is the primary action, and a day that cannot be approved yet shows a disabled Approve day with the reason inline.
AI observationThis version does the job: an admin can see what is left, who is blocking payroll, and the one action that unblocks it, and nothing from the old page was lost. What remained was making it feel like the rest of BRICK. The summary still sat in its own card, and the page did not share the same left and right edges as the other BRICK pages being refined at the same time.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Let the summary sit open on the page instead of inside a card, and keep the review table as the one white sheet.
What the AI changedThe summary now sits open on the page above the review sheet, the page shares the same left and right rails as the other BRICK pages, and every sidebar group opens into sub-items the same way Time tracking does.
AI observationNow the one white surface is the list of workers who need a decision, so the eye goes straight to the work. The numbers above it read as context, not as another box to process, and the page feels like part of one BRICK system instead of a one-off screen.
Rule to take with youA redesign that drops real actions is a regression, however clean it looks. Keep every control, then lead with what blocks the decision.



Sellfyi · selling options
Who uses it and whyMarketplace owners use this page to set how vendors can sell: uploads, commission, and order and product rules, then save.
3 versions
AI observationThis page was one long list of checkboxes, with long sentences and short labels at the same weight, under a dark sidebar plus a second settings menu. Nothing was grouped by topic and there was no visible save state, so an owner could not tell whether a change was live.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding.
What the AI changedSettings were grouped into New vendors, Commission, and Products and orders, with switches and dropdowns on the right and a Discard and Apply Change bar.
AI observationGrouping made the page far easier to scan, and owners could now find a rule by topic. Two things still got in the way. The page was split into two cards, and Discard and Apply Change stayed active even when nothing had changed, which leaves people unsure whether their settings are saved. The next step was one panel with an honest save state.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Merge the two cards into one panel with a thin divider and a warm settings sub-nav. Use rows with the label on the left and the control on the right, with no boxes around rows. Add a save bar that says All changes saved, and disable Discard and Apply when there is nothing to save.
What the AI changedTwo cards became one panel. Rows are 56px with the label left and the control right, the settings sub-nav is warm and quiet, and the save bar reads All changes saved with its buttons disabled until something changes.
AI observationNow it reads like a calm admin form. Each row is one decision, grouped under clear headings. Most of all, the save bar tells the truth, so owners know exactly when a change is live and when it still needs applying.
Rule to take with youA settings page must always show whether a change is saved. Buttons that stay active when nothing has changed make people doubt every setting.



BRICK · estimate details
Who uses it and whyEstimators open this page right before sending, to check who the estimate is for, where the job is, and the company details on the letterhead.
3 versions
AI observationThis page opened with a More Options menu full of template prompts and exports, a large company contact card with a big logo, and a nested project financials box. The two things an estimator checks before sending, the customer and the job address, were not the first things you saw.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Treat this as a document that gets sent. Keep every action and piece of content, keep it consistent with the estimate section page, and never show Projul or Sound.
What the AI changedOne header line now says the status, who it is for, the project, the dates and who prepared it. Customer and company details open in place, with call, email and map actions beside the values. Totals sit right below, and Resend estimate is the one primary action.
Masum's thoughtThis version reframed the page around sending, which is exactly the job. My notes for the next pass were about the header. The profile picture would fit better here, beside the customer's name, and the sales rep needs no highlighted background. On this page and the estimate section page, the text was a little hard to read over the pattern.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Put the customer's photo next to their name in the header line. The Customer and company toggle expands a section, so it should not look like a button. Fade the header pattern from fully visible at the top to 15% at the bottom.
What the AI changedThe customer's photo now sits beside their name. Customer details, totals and the pricing list joined into one continuous sheet instead of three boxes, and Estimates opens into All, Draft, Pending and Accepted in the sidebar.
AI observationNow an estimator can confirm the essentials in one sweep down a single sheet: who and where, then the money, then the sections. Each identity detail appears once, so nothing has to be cross-checked before pressing Resend estimate.
Rule to take with youBefore something is sent, show who and where first, and say each identity detail once.



BRICK · invoice
Who uses it and whyProject managers and billing staff use this page to build a progress invoice: decide what share of the estimate to bill plus extras, check the total, and send it.
3 versions
AI observationThis was a very long page of stacked sections: company contact, customer and project info, project financials, invoice details, introduction, two invoice options, line items, contract details, attachments and payment options. The amount due was buried deep in the scroll, and Send sat at the very bottom.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Give the page one path to the amount due and then Review and send. Keep BRICK, and never show Projul.
What the AI changedThe long form became a billing flow: pick the percentage, see what was billed before, after and what remains, add extra charges, then review a summary with the amount due and Review and send.
AI observationThat is the right order, and billing staff can now follow it without hunting. But it lived in five stacked cards, with the summary framed as a zig-zag receipt box, so it felt like a checklist rather than one invoice. The total also scrolled away while you edited the steps above it.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Merge the five cards into one white invoice sheet with sections split by thin lines. Put the summary open beside the sheet, with no receipt-style card. End the flow in one blue Review and send.
What the AI changedFive cards became one white sheet with hairline sections. The summary now sits open beside it with no receipt chrome, and one blue Review and send closes the flow.
AI observationNow it reads as one invoice being built. Every decision sits in order on the left, and the amount due updates on the right as you go, so the total is always in view while editing. Billing staff never lose sight of the number they are about to send.
Rule to take with youWhen people build a total step by step, keep that total in view the whole time.



Reports overview
Who uses it and whyBusiness leaders use this page to see how the store did this year against last year, then which categories and products drove it.
3 versions
AI observationThis version had four KPI cards, one Order Analytics chart and two product tables in separate floating panels. The yearly comparison was only partly visible, so a leader had to hunt for the answer instead of reading it top to bottom.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Order the page by the questions a leader asks: how did we do, where did it come from, and which products drove it.
What the AI changedThe page now follows that order: KPIs with last year beside them, orders by month against last year, revenue by category, then top products.
Masum's thoughtThe order was right. My question for the next pass was about space. Why are we leaving this white, empty space here, when more content should be shown to the users? And why leave the bottom empty when the table could run to the end?
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Use one white canvas with no cards: the KPI strip, then the two charts, then ranked products. Use the empty space for more product rows and let the table run to the end of the sheet. Keep the current Reports mark.
What the AI changedEverything moved onto one white canvas with no cards. The ranked product table now runs to the end of the sheet and shows eight products instead of four.
AI observationNow the page answers a leader's three questions in order, on one canvas. The numbers come first, the charts explain where the change came from, and the product table uses the space that used to be empty, so people get twice the answers with no extra clicks.
Rule to take with youEmpty space on a report is a question left unanswered. Fill it with the next useful rows.



BRICK · estimate section
Who uses it and whyEstimators use this page to price a section line by line and check margin before sending.
3 versions
AI observationOpening one cost item dropped you into a deep grey panel with a receipt-like calculation and a long column of toggles and fields, while the running total sat far from the line being edited. Long estimates felt fragile, because you lost sight of the total the moment you started pricing.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Keep this page consistent with estimate details. Use the approved summary card for totals rather than an invented receipt rail, and never show Projul or Sound.
What the AI changedThe grey summary rail and the torn-receipt card were removed. Estimated total, subtotal and company costs sit at the top, the open section lists each line with type, quantity, price and real Tax and Visible toggles, drag and expand came back, and Resend estimate is the one primary action.
Masum's thoughtThe total was finally visible while pricing, which is the whole point. My next notes were about using space well. Long descriptions should use ... after a limit. We have enough space at the left, so why did we tighten this information? And the text was hard to read over the header pattern on this page and on estimate details.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Truncate long descriptions with an ellipsis, and give the columns their width back where there is room. Fade the header pattern from fully visible at the top to 15% at the bottom.
What the AI changedThe totals and the pricing list now share one continuous sheet, the line columns have more room, and Estimates opens into All, Draft, Pending and Accepted in the sidebar.
AI observationNow the money and the lines being priced live on the same surface, so an estimator edits a line and sees the total and margin above it without the page breaking into boxes. Knowing where this estimate sits in the pipeline is one glance at the sidebar.
Rule to take with youWhile people edit money, the running total should never leave the screen, and long text should never squeeze the numbers.



Organization settings
Who uses it and whyAdmins use this page to check and change the organization's identity, AI features and publishing setup.
3 versions
AI observationEvery setting had a bright coloured icon tile, toggles and buttons carried the same weight, and risky publishing changes like subdomain and custom domain sat at the same level as cosmetic ones. It was hard to scan, and an admin could not find one setting quickly.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep the sidebar clean with no extras, and do not put icons on coloured or grey circles.
What the AI changedThe page was grouped into Organization profile, AI features and Publishing, each with clear labels and help text.
AI observationGrouping made the page easy to scan, and admins could now find a setting by its area. It still used three cards and a grey circle behind every icon, so it looked busier than a settings page needs to be. The next step was one calm sheet where labels and controls line up.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Merge the three cards into one settings sheet. Remove the icons on grey circles. Put the label and help text on the left and the control on the right. Show the subdomain in a monospace font so it reads as an address.
What the AI changedThree cards became one settings sheet. The icon circles are gone, every row has label and help on the left and a control on the right, the nav uses a soft grey active state, and the subdomain is set in monospace.
AI observationNow it is one quiet sheet. With the icon circles gone, the eye goes straight to the setting names, and the monospace subdomain makes the publishing address easy to check before anyone changes it.
Rule to take with youIn admin settings, the label is the navigation. Remove anything that competes with it, and make addresses look like addresses.



BRICK · time logs
Who uses it and whyAdmins use this list after a pay period closes to scan the crew and decide whose time to open and approve first.
3 versions
Masum's thoughtAn earlier pass on this page didn't look like a UX redesign; it just copied the old design. The page, its content and its context had not been understood. The old list stacked one big block per worker, every worker looked the same, and there was no way to see who needed review first.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Understand the page, its content and context first. Keep this list on the same shell and data as time log details, and make every row show the problem and the next action. Remember the changes we made there, the date filter, the sidebar and the breadcrumb, and apply them here too.
What the AI changedThe list became a review queue on the same shell as time log details. Left to approve leads, Needs your review lists each worker with a plain description of the issue and the action that fixes it, and Approved sits below with no repeated 0h.
AI observationThis version works as a queue: the admin knows who to open first and why. The remaining gap was the same one across all the BRICK pages at that point. The summary sat in its own card, and the page did not yet share the left and right edges of its sibling pages, so moving between them felt slightly uneven.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Let the summary sit open on the page, and keep the needs-review rows above the approved ones.
What the AI changedThe summary now sits open above the list, the page shares its rails with time log details, and the sidebar groups all open into sub-items the same way.
AI observationNow it works as a to-do list for payroll. The admin sees how much is left to approve, then the workers who need review, each with what is wrong and the one action that fixes it. Because it matches time log details exactly, opening one worker feels like going deeper, not switching tools.
Rule to take with youA review list should be finishable. Every row says what is wrong and what fixes it, and solved rows step aside.



BRICK · estimates
Who uses it and whySales and project teams use this page to see where each estimate stands (sent, accepted, invoiced, paid) and take its next step.
3 versions
AI observationEstimates were a grid of cards, each with a different layout inside: some with a donut, some with totals, some with a list of draws. Comparing money across estimates meant jumping between card shapes, and the status tab totals at the top could disagree with what the cards showed.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Keep it as simple as possible. Numbers must reconcile, and each estimate should show one next step.
What the AI changedThe cards were cleaned up and each estimate gained a breakdown bar, with status tabs for All, Draft, Pending and Accepted above the grid.
Masum's thoughtEach estimate became easier to read on its own. For the next pass I pushed on navigation and space. Why don't we move these tabs into the sidebar submenu, like we did for People? We don't need a whole empty white area just for the search box. And All, but how many estimates are in All? The sheet should not leave empty strips either.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Replace the card grid with one comparative list in a single sheet. Lead with drafts and pending estimates, and align the money and action columns. Move the status filters into the sidebar as sub-items with a breadcrumb, give All a truthful count, and place search in the header instead of its own empty card.
What the AI changedThe card grid became one list with shared columns for total, invoiced, to be invoiced, paid and due. Drafts and pending estimates lead, status filters moved to the sidebar with counts, and search sits in the header.
AI observationNow estimates are easy to compare, because money reads down a column instead of across card shapes. Drafts and pending ones lead with Review and send or Follow up with client, and the sidebar counts match the list, so the team can trust the numbers they act on.
Rule to take with youIf people need to compare money, use a list with shared columns, and make every count match what is on screen.



Marketplace
Who uses it and whyData teams use this page to pick tools or bundles for their workspace and launch what is ready.
3 versions
AI observationBundles and services sat as floating cards with placeholder text, repeated tool lists, and price chips that looked like buttons. The accent colour was used on several things at once, so nothing clearly said "launch this".
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. This page is the Leel.Data style reference, in my words "a page was already set with style, the redesigned one", so keep that shell. Sell the job each add-on does, and use the accent colour only for real launch actions.
What the AI changedEvery bundle got a real description, its tools and a price, trending services became a clear table, and Launch became the only orange action.
Masum's thoughtThe catalogue made sense now. My concern for the next pass was trust. Some logos were blank, a few were broken or off-centre, and the logo and the name should always match, so never use empty logos. I also asked to avoid bad shadows and use a softer stroke instead, and to reduce the corner rounding by 30 to 36%.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Turn the floating cards into quiet grids divided by thin lines, and make trending a simple list. Use real logos from Hugeicons or the current assets, centred and matching their names. Replace drop shadows with a soft ring, and keep orange for launch actions only.
What the AI changedFloating cards became two hairline grids and trending became a list. Every tool shows a real, centred logo that matches its name, drop shadows became a soft ring, the copied Data Fusion bundle content was fixed, and orange is used only for Launch.
AI observationNow it reads like a calm catalogue. Every tile has the same structure: name, what it does, the tools inside, price and one Add action. Real logos make each tool recognisable at a glance, and the single orange Launch tells the user exactly what is ready to start.
Rule to take with youIn a marketplace, recognition is trust. Real logos that match their names matter more than any decoration.



BRICK · portal invoice paid
Who uses it and whyHomeowners use this page after paying to confirm the payment worked, keep the receipt, and see what is owed next.
3 versions
AI observationThe page showed the contractor's contact block, the customer and project block, and a small invoice details row with a Paid tag. Proof of payment was a tiny label, there was no way to get a receipt, and nothing told the homeowner what comes next.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Follow the portal rules: the customer never sees costs or markup, and the portal shell stays consistent across every portal page. Rebuild around reassurance, with proof first, and say each fact once.
What the AI changedThe amount paid now leads, with the date, card, fee and confirmation number, and Download receipt is the one blue action. A breadcrumb replaced the bare back arrow, repeated invoice numbers and Paid lines were removed, the overdue next invoice became a short note with a pay link, and a billing strip shows invoiced, paid and $17,103.88 left to bill.
AI observationThis version already does the emotional job well: proof first, receipt one click away, and the next thing owed stated calmly. Because it was already in good shape, the next pass was about consistency rather than structure, bringing it onto the same rails and spacing as the BRICK pages being refined at the same time.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Keep the structure, and keep the portal shell consistent with the other portal pages.
What the AI changedThe structure stayed the same. The page moved onto the shared BRICK rails, the overdue note gives its pay link a line of its own, and the billing strip splits invoiced, paid and left to bill into divided cells.
AI observationThe page still answers the homeowner's three questions in order: did my payment go through, where is my receipt, and what is next. Leaving a working structure alone and only aligning it with the system was the right call here.
Rule to take with youAfter someone pays, give proof first, say each fact once, and show what comes next. When a page already does that, refine it; don't redesign it.



BRICK · time tracking
Who uses it and whyCrew members use this page to see what they are clocked into, clock out or switch task, and check today's hours.
3 versions
AI observationA black timer box sat off to the right, beside a column of large task cards, each with its own Clock in button and contact details, under a Track your hours dropdown title. The running clock was not the main thing on the page, and the day's schedule was hard to read through all the boxes.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. The timer is the main moment on this page. Keep the crew title Track your hours under Time tracking.
What the AI changedThe clock became the hero: what you are clocked into, the running time and one Clock out, with today's schedule underneath and a Switch action on each task.
Masum's thoughtThe clock finally led the page. My next direction was navigation and weight. The Track your hours dropdown should become a breadcrumb, Time tracking › Track hours, with sidebar sub-items. And panels like the notes panel are sub important, not the main items on the page, so we should leave them without a card.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Use a flat clock strip with one blue Clock out. Put today's schedule in one sheet with a Now tag on the active task. Move notes into an open rail with no card. Use Time tracking › Track hours as the breadcrumb and apply it across the Track hours pages.
What the AI changedThe clock became a flat strip with one blue Clock out. Today's schedule is one sheet with a Now tag on the active task, notes moved into an open rail, and the title became the Time tracking › Track hours breadcrumb.
AI observationNow the running clock and the active task sit in one line at the top, with today's and this week's hours beside them. The schedule reads as a timeline, and notes sit open on the right for quick context without competing with the clock.
Rule to take with youWhen time is running, the clock and the active task are the page. Secondary panels should never be boxed like main ones.



Leel.Data · workspace
Who uses it and whyData teams landing in a workspace use this page to resolve issues, check connected apps, and track budget and team ownership.
3 versions
AI observationThis was a widget collage: a client details table, a budget donut, an apps list and a team list, all as equal panels. Nothing said what needed attention, so landing in the workspace meant reading every panel to find out whether anything was wrong.
To the AIRedesign the latest approved version again. Avoid card styles except where a surface is truly needed. This is a B2B SaaS product, so keep corners tight and avoid too much rounding. Use the same Leel shell as Marketplace. When an Overview pass came back in a different style, I pointed back: "a page was already set with style, the redesigned one." Orientation first, less widget noise.
What the AI changedThe workspace was reorganised around status. Apps show running, connecting or token-expiring states, Needs attention lists failures with one action each, and the budget is projected for the month.
AI observationThis version was far more useful the moment you landed, because it told you what was healthy and what was not. The next step was to put issues clearly first, make the apps read like a ledger people can scan for status and cost, and match the Marketplace shell and real logos so the two pages feel like one product.
To the AIFollow my Design Taste V.2 file and every comment on it: a clean sidebar with no vertical line, a very soft background, white only where people need to look, very subtle shadows, and buttons with less rounding. Visit the products behind my reference screenshots and study their shadows, colours, cards and corner rounding before redesigning. Lead with what needs attention. Show apps as a ledger with status, owner and cost per row. Open the budget as a band, and keep organisation and team as an unboxed rail. Share the Marketplace shell, and use real logos with the same rule as Marketplace, never empty ones.
What the AI changedNeeds attention now leads, apps became a ledger with status, owner and cost, the budget opened into a band, and organisation and team sit in an unboxed rail inside the shared Marketplace shell with real logos.
AI observationNow the page orients the user first. A failed pipeline or an expiring token is the first thing you see, each with its fix beside it. The apps ledger then shows what is running and what it costs, and moving between this page and Marketplace feels like one product.
Rule to take with youA workspace home should answer "is anything wrong?" before it shows anything else.



BRICK · track hours (multiple)
Who uses it and whyCrew members use this page to clock into the task scheduled now and track today's and this week's hours across several tasks.
3 versions
AI observationThe same large task card repeated three times, each with its own Clock in button, contact block and Show more log details link, beside a black timer and a stack of note cards. The repeated fields took more room than the work itself, and the next task was hard to spot.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Use the approved BRICK shell with Time tracking › Track hours as the breadcrumb. Panels like the notes panel are sub important, not the main items on the page, so leave them without a card.
What the AI changedThe page became a real clock-in page: Not clocked in with when the next task starts, one Clock in button, worked today and this week beside it, and today's schedule as a timeline with Done, Up next and Clock in states. Notes sit open on the right without a card.
Masum's thoughtThis was the right shape for a crew member starting their day. My remaining notes were about weight and alignment. Why do we need this line here? It looks extra. And the notes box could align from the top with the card on the left.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Remove the extra lines, align the notes to the top of the schedule, and let the clock summary sit open on the page.
What the AI changedThe clock summary now sits open on the page instead of inside a card, the notes line up with the top of the schedule, the Up next task is softly highlighted under the Now line, and each note leads with its time.
AI observationNow the page tells the crew member the one thing they need: you are not clocked in, the next task starts at 11:30, clock in here. The highlighted Up next row connects that message to the schedule, and the notes are there when needed without pulling focus from the clock.
Rule to take with youOn a clock-in page, the next task and one button lead. Supporting notes stay open and quiet beside them.



BRICK · customers
Who uses it and whyOffice staff use this page to find customer documents that need action (collect, remind or send) and act on them in one click.
3 versions
AI observationThis page was a phone book. Every row had the same weight, customers repeated with the same project, and actions like Send estimate, Send receipt and View change order were small blue text. Nothing showed which customer owed money or what to do first.
To the AIRedesign this page around the task the person came to do. Reuse the approved BRICK components 1:1, use realistic content, and never show the Projul name. Keep the People customers content. Rebuild around follow-up, make the work that needs action obvious, and avoid a grid of cards.
What the AI changedThe list became a follow-up queue. To collect leads the summary, a Needs action group comes first with what is wrong and the right next step on each row, such as Send reminder for an invoice already sent, and No action needed sits below.
Masum's thoughtNow the page worked as a queue, not a directory. My next direction was navigation and grouping. Why are Customers and Employees not going under the sidebar menu and becoming a breadcrumb, like we did for time tracking? The spacing after Needs action was too much, and relevant items should be grouped meaningfully. The right side should share the same spacing as the left.
To the AIApply the same feedback to all the BRICK projects as After V.2. Put every page on one shared left and right rail, so the items above a sheet line up with its edges and the action buttons sit on the right edge. Keep cards only where they are truly needed. Use People › Customers as the breadcrumb, with Customers and Employees as sidebar sub-items. Tighten the Needs action group. Use square tags with 2 to 4px corners, light count badges that match the Send reminder button, and one aligned Action column.
What the AI changedPeople › Customers became the breadcrumb with Customers and Employees as sidebar sub-items, the tab row is gone, the Needs action group was tightened, and the summary and table now share the same left and right edges.
AI observationNow it works as a collections and follow-up desk. Money to collect leads, then seven documents that need action sit in one tight group, each with what is wrong, how late it is and one correct next step. Office staff move between People pages the same way they move everywhere else in BRICK.
Rule to take with youA customer list is a follow-up queue, not a directory. Lead with the money to collect and the next step for each person.

In 11+ years of designing, Masum has learned that design is really about people: how they think, what they trust, and why they stay. He uses that to help founders build products where great UX and business goals work together.
On every Halal Lab project, Masum is your lead designer. He sets the direction and makes the key design calls, and his team works alongside him so the work moves fast without losing quality.
He also built Hugeicons, an icon library used by over a million designers and developers.
Masum transformed our data-heavy product into a clean, intuitive experience. His design decisions were thoughtful, efficient, and optimized for constrained layouts. Highly recommended.

Richard Jackson
CEO & Co-Founder, Alphaletz.com

#NOTEMasum paused client work for 2–3 years to build Hugeicons. Now that it’s stable, he’s back taking on UI/UX projects, starting October 2026.