UX case study 04 / Fintech · SaaS
Designing a clearer experience for everyday business finance.
A UX case study exploring how business owners and accounting professionals move through billing, inventory and GST-related tasks—and how a clearer, more connected experience could help them work with greater confidence.
01 / Context & scope
Understand the product before redesigning the experience.
Skybiller presents itself as a cloud-based accounting application for small and growing businesses. Its public product messaging brings together GST-ready billing, income and expense tracking, inventory, payment follow-ups, e-invoices and e-Way Bills. The website also speaks to accountants and GST consultants who manage records and filings across multiple clients.
Run the day-to-day
Create invoices and quotes, keep track of dues, record expenses, manage stock and understand business finances from one place.
Manage multiple clients
Bring client billing, stock and accounting records into a shared operating workflow, with GST preparation as a central job.
Keep work moving
Connect transactions with inventory and payment status, and reduce the need to jump between disconnected tasks.
Prepare with confidence
Support GST reporting and filing workflows, plus e-invoicing and e-Way Bill generation as described on the public website.
Product thesis
Make the next best action clear—create, send, reconcile, follow up or prepare a filing—while keeping the underlying financial record accurate and traceable.
02 / Problem framing
Accounting is a system of connected tasks—not isolated screens.
For a small business, a sale may begin with a quote, become an invoice, update stock, create a receivable and later require a payment follow-up or GST reporting. When these steps are difficult to see as one journey, users can lose context, repeat data entry or miss a required action.
For accountants and GST consultants, the challenge expands across multiple businesses, records, deadlines and exceptions. The opportunity for Skybiller is to make the relationships between transactions, stock, outstanding dues and compliance tasks easier to understand.
How might we…
Help business owners and accounting professionals complete routine financial work with fewer context switches, clearer status and more confidence in what needs attention next?
UX portfolio integrity: this is a hypothesis-led problem framing unless you can support it with real research notes, customer feedback or usability findings. Clearly label what you observed versus what you propose.
03 / Users & tasks
Design around the job, the role and the business context.
Keep the business moving
Needs: create bills quickly, see who owes money, track expenses and stock, and understand current financial status without accounting jargon.
Maintain clean records
Needs: review transactions, identify missing information, reconcile records and prepare reliable reports across client accounts.
Prepare and review filings
Needs: organize client records, spot exceptions early, validate tax-relevant information and know which filing tasks remain.
Reflect how the business operates
Needs: workflows that account for different product, stock, pricing and record-keeping practices, including the IT businesses and gold merchants relevant to this project context.
These are working audience models based on product positioning and the project context. Label them as personas only after confirming them with research participants or stakeholders.
04 / UX benchmarking
Benchmark experiences—not just feature lists.
Zoho Books and Xero establish familiar expectations for modern cloud accounting: invoicing, expense and bill management, financial reporting, inventory capabilities and bank reconciliation. Zoho Books also highlights India-specific GST and e-invoicing workflows. Skybiller should therefore make its audience fit, day-to-day workflow and local compliance experience tangible rather than rely on broad “all-in-one” messaging.
| Dimension | Skybiller opportunity | Portfolio/design implication |
|---|---|---|
| India-first compliance | Public messaging emphasizes GST workflows, e-invoices and e-Way Bills. | Make filing readiness, missing data, validation errors and next steps visible. Confirm exact integrations and filing capabilities before making claims. |
| Connected billing & stock | Public messaging combines invoicing with real-time inventory and accounting. | Show how a transaction affects stock, receivables and reports; keep system feedback clear. |
| Payment follow-up | Public messaging mentions automated reminders via WhatsApp and tracking outstanding dues. | Make invoice status, due dates, follow-up history and the next action easy to scan. |
| Accountant / consultant workflows | Skybiller explicitly addresses accountants and GST consultants managing multiple clients. | Prioritize client switching, portfolio-level status, exceptions and repeatable review tasks if supported by the product. |
| Trust & usability | Financial software needs users to understand what changed and why. | Use precise language, visible audit context, clear permissions and recoverable error states. |
Competitive references: Skybiller, Zoho Books India and Xero. This is a strategic comparison of publicly described positioning, not a feature-by-feature product audit.
05 / UX principles
Make complex financial work feel manageable.
Lead with what needs attention
Prioritize overdue invoices, filing tasks, unreconciled items and exceptions over dashboards filled with undifferentiated numbers.
Connect the record to the action
Let users move from an invoice or transaction directly to relevant payment, stock, customer or reporting context.
Explain compliance states
Use understandable status labels, explicit prerequisites and actionable error messages instead of opaque success or failure signals.
Support both speed and review
Make common tasks efficient for business owners while giving accounting professionals enough detail to inspect and correct records.
Treat these as proposed design principles unless they accurately describe decisions made during the original project. Add your real sketches, flows, iterations and rationale to demonstrate how the principles shaped the shipped experience.
06 / User flows
Design around the tasks users need to finish.
Quote → Invoice → Payment
Capture customer and item details, review tax and totals, send the invoice, track due status and follow up on outstanding payments.
Item → Transaction → Stock
Keep item information consistent as sales and purchases affect stock; show users when an item or quantity needs attention.
Expense → Record → Report
Record business expenses, attach supporting information where supported, and make the resulting entry easy to find in financial summaries.
Transactions → Review → Filing
Help users understand data readiness, find missing or inconsistent information and review outputs before submitting a return.
Use these flows to explain task structure. In the final case study, show your actual flow diagram, decision points, edge cases and iterations. Keep only steps that match Skybiller’s real product behavior.
06A / Information architecture & wireframes
Help users understand where they are—and what comes next.
A useful UX artifact for this product is a task-first information architecture that groups work by the user’s intent. The structure below is a proposed starting point; validate it against the current product, user terminology and real workflows before treating it as the final navigation.
Work by intent
Overview · Sales · Purchases & expenses · Items & inventory · Banking / reconciliation where supported · Reports · GST / compliance · Settings.
Keep related actions together
For example: invoice list → invoice detail → payment status → reminder history. Keep the record and its next action connected.
Wireframes to show in the portfolio: (1) dashboard with prioritized actions, (2) invoice creation, (3) invoice detail and payment follow-up, (4) item / stock detail, and (5) GST readiness or exception review. Add low-fidelity sketches and annotate the decisions that changed after feedback.
The information architecture and screen list are proposed UX artifacts, not a claim that these exact designs shipped in Skybiller. Replace them with your actual sitemap, wireframes and product screenshots where available.
07 / Interaction & UI design
Small interaction details carry financial weight.
- Accuracy before decoration: make amounts, tax treatment, due dates and status easy to review.
- Progressive disclosure: show the fields needed for the current task, while keeping advanced accounting details available when relevant.
- Useful feedback: explain whether a transaction is saved, sent, pending, overdue, reconciled or needs correction.
- Safe recovery: prevent accidental destructive actions and give users a clear way to correct mistakes.
- Accessible data density: use consistent alignment, labels, contrast and responsive tables for financial information.
- Permission-aware collaboration: make it clear which business or client context a user is working in, where multi-client access is supported.
For visuals, use approved product screenshots or rebuild the screens with synthetic names, GSTINs, invoice numbers and financial values. Annotate the interface to explain the user problem, the decision and the trade-off.
08 / Usability testing & outcomes
Validate the experience with evidence.
A credible portfolio case study separates what was delivered from what was measured. If historical analytics are available, select a small set of measures tied to the workflow rather than adding unsupported success percentages.
Suggested validation plan: test one end-to-end billing flow with business owners, one record-review flow with accountants, and one GST preparation flow with a qualified domain expert. Include task success, observed friction and the design changes made after each test.
No quantitative outcomes are asserted here because verified project metrics were not provided. Add only results supported by analytics, research notes, stakeholder feedback or documented delivery evidence.
09 / Reflection & next steps
Make the design reasoning visible.
Skybiller is a useful case study for showing how product design connects operational tasks, industry context and compliance-sensitive workflows. The strongest portfolio version will make the design reasoning visible: the initial problem, the evidence gathered, the options considered, the decisions made, and what changed as a result.
Before publishing
Confirm your exact role and dates, which screens or workflows you personally designed, who else contributed, what research actually took place, and which product outcomes can be substantiated. The audience and strategy sections above are a structured narrative based on public product positioning; they should not be presented as completed research or measured results unless you can verify them.
Respect customer confidentiality. Do not publish real financial records, customer details, credentials, private analytics or unapproved screenshots. Use synthetic data for public mockups.
More selected work