ALL PROJECTS

06 / Fintech + Transactional UX

Crediflow

A guided business lending journey with clear requirements, decision states and next steps.

PROJECT STUDY
  1. 01PAN / GST / ITR
  2. 02FINANCIAL ASSESSMENT
  3. 03APPLICATION STATE
PAN / GST / ITRFINANCIAL ASSESSMENTAPPLICATION STATEBusinessinformation01DOCUMENTS02ELIGIBILITY03REVIEWHUMAN REVIEW

PRODUCT MAP / Complex workflow design + fintech UX

02 / Overview

From application to disbursement.

Crediflow brings application, financial documents, assessment, eligibility, approval and disbursement into one guided digital experience. Applicants provide business details and supporting financial information in stages, then move toward a credit decision. The product focuses on making that progression understandable, so a person can see what is needed now and what comes next.

03 / THE PROBLEM

Borrowing for a business comes with a lot of paperwork.

A business loan can require identity information, GST records, several years of tax returns, bank statements and detailed business information before eligibility can be assessed. Collecting that material takes effort. The experience needed to make the requirements manageable while giving applicants a clear sense of what had been received, what remained and where they were in the process.

04 / Defining the product

Make each requirement part of the journey.

I followed the applicant’s path from starting an application through documents, assessment and the credit decision. Document collection is a stage of that path, rather than a separate administrative task. The interface needs to explain why information is requested and distinguish completing the application from being assessed, approved or ready for disbursement.

Ask what is needed now
Collect business information progressively. A person should not have to understand every later stage before they can begin the application.
Make document requirements clear
Name the required PAN, GST records, three years of ITR and bank statements. Show what is needed, why it matters, what has arrived and what remains.
Show progression and decisions
Assessment, eligibility, approval and disbursement are distinct states. Each needs a clear explanation and a next step, without implying that progress guarantees approval.

05 / Designing the system

One application, a clear path forward.

The journey keeps the lending stages in a readable sequence. Business details and documents support financial assessment; eligibility and approval communicate the decision before disbursement. This is an applicant view of the process, designed to explain progress without making the person navigate the technical machinery behind a credit assessment.

  1. 01Application
  2. 02Documents
  3. 03Assessment
  4. 04Eligibility
  5. 05Approval
  6. 06Disbursement

Applicant journey / requirements, decisions and next steps

06 / Key product challenges

The decisions that shaped the product.

Application progress is not a credit decision.

The thinking
An applicant can complete every requested upload and still be waiting for assessment. Treating those events as one success state would obscure what had been decided and what remained uncertain.
The decision
Separate information collection, assessment, eligibility, approval and disbursement. Each state explains what has happened and what the applicant can do next.
The result
The status model makes completion of a task visible without suggesting that completing an application guarantees approval.

07 / The solution

Make progress clear from the first requirement.

JOURNEY 01

How do you make paperwork feel like progress?

Document requirements are work the applicant can complete within the lending journey. The experience needs to show the relevant document, the required period and its current state, rather than presenting every file as an identical upload task.

Business identity and records
PAN and GST information establish the business context. Requirements should name the information needed and explain its place in the application.
Financial history
Three years of ITR and bank statements support the financial assessment. Keep the required periods explicit so an applicant can distinguish a complete submission from a missing year or statement.
Received, outstanding, needing attention
An uploaded file is distinct from information accepted for assessment. A missing or unsuitable document needs a specific correction path that preserves the rest of the application.

JOURNEY 02

Understand the decision before moving forward.

After information collection, the interface shifts from asking for documents to explaining assessment and decisions. Applicants and operational reviewers need different views of that work, but both should refer to a consistent application state.

Under assessment
Explain that review is in progress and whether further information is required. The applicant needs a next step when there is work to do, and a clear waiting state when there is not.
Eligibility and offer
Keep eligibility, approval and the offer distinct. The applicant needs to understand what has been decided and what still requires review or acceptance before moving forward.
Decision and disbursement
An approval should not imply that money has already been disbursed. If the application cannot proceed, explain the decision state and any available next action without presenting it as successful completion.

08 / Outcome & impact

A clear application and decision state model.

My contribution was structuring document collection and lending progression into understandable requirements, states and next actions. The design distinguishes a received document from one accepted for assessment, and a completed application from an approved or disbursed loan. Those distinctions give applicants a practical way to understand progress while keeping the financial decision separate from task completion.

Clarity through the process
Document progress and decision states share one guided journey, so applicants can understand both what they have completed and what comes next.
What I learned
A complex process does not always need fewer steps. It needs clearer progression between them. Keeping collection, assessment and approval distinct helped me focus on the information someone needs at each point, instead of treating a shorter flow as the only measure of a better experience.

09 / Success criteria

Success criteria: measure completeness and status clarity.

Evaluate whether applicants understand requirements, submit usable information and know the difference between application progress and a lending decision.

Submission completeness
≥95%

Applications containing the requested information and correct document periods when submitted for assessment.

Correction effort
≤1 round

Correction cycles needed to resolve missing or unsuitable documents while preserving the rest of the application.

Status comprehension
≥95%

Applicants correctly distinguishing assessment, eligibility, approval and disbursement, and identifying their next action.

10 / NEXT PROJECT

EIGNA

Properties, tenants and everyday operations. In one place.

UNIT 01OCCUPIEDUNIT 02OCCUPIEDUNIT 03VACANT11,200LEASE ACTIVE
PROPERTY RECORDOne property.
Every operation.

TENANT / LEASE / INSPECTION
RENT / MAINTENANCE / FINANCIALS

ALL PROJECTSTHE THREAD CONTINUES