“What are my options, and what do I need to do next?”
A borrower compares a product, starts an application, provides supporting information, follows its progress, reviews an offer and later manages repayments or asks for help.
← The guided build series
Phase 0 / The big idea
Meet the lending marketplace we’re going to build.
A clearer way for people who need funding, people who provide it and the teams who make the process work.
This is the starting point: a plain-English introduction to the product, its people and the principles that will guide every later phase.
Product marketing introduction · Fictional users · Simulated money · ClearLend is a working name
01 / The vision
Make a complicated journey easier to understand.
Borrowing money can involve forms, evidence, decisions, agreements, funding and months of repayments. When those steps are spread across different conversations and systems, people lose track of what is happening.
Our application will bring the journey into one connected place. A borrower can understand the options and follow a request. A funding partner can see what capital is committed. The operations team can move each case forward with the right evidence and authority.
Good software should make progress visible, decisions explainable and responsibility clear.
This is a product and engineering project led by Afzal Ahmed, a senior ASP.NET and full-stack engineer with long experience building and supporting business-critical applications.
02 / The main characters
Three people. One shared story.
You do not need to be a finance expert to follow this product. Think of it as a carefully managed journey where each person sees the information and actions relevant to them.
“What am I committing, and what has actually happened?”
A funding partner sets their capacity and preferences, considers suitable opportunities, commits capital and follows the difference between reserved money, active exposure and money actually received.
“What evidence supports this decision, and who owns the next action?”
Operations verify information, review applications, prepare offers, oversee funding, handle exceptions and keep a reliable history that another colleague can understand.
03 / The journey
From a question to a clear outcome.
The application will grow through phases, but the story remains connected.
- 01
Explore
A borrower understands products, amounts, costs and the assumptions behind an illustration.
- 02
Apply
They save a draft, provide information and submit a request that the operations team can review.
- 03
Assess
A named reviewer checks the evidence, asks for what is missing and records a reasoned decision.
- 04
Agree
The borrower reviews the exact offer and accepts it; approval and acceptance remain separate.
- 05
Fund
A funding partner considers the opportunity and records a commitment; a commitment is not yet a payment.
- 06
Manage
Later phases follow repayments, support, changes, exceptions and closure.
An approval is not an accepted offer. An accepted offer is not a funding commitment. A commitment is not proof that money moved. Keeping those moments distinct is central to making the product trustworthy.
04 / How we will build it
Principles people can feel in the experience.
- Clarity before complexity. Explain the current position, outstanding work and next action in everyday language.
- Evidence before assertion. Decisions should show what was considered and who made them.
- Permission with purpose. A person should see and change only what their responsibility allows.
- History that can be trusted. Corrections and uncertain outcomes stay visible instead of being quietly overwritten.
- Human support when the path changes. Missing information, delays and exceptions are part of real journeys and deserve a clear response.
05 / What the application will do
Useful features, explained simply.
Compare products
See understandable illustrations of amounts, costs, terms and important conditions.
Build an application
Save progress, provide information, respond to requests and know whether the case is ready for review.
Make accountable decisions
Review evidence, record reasons and issue a clear offer with its exact terms.
Track commitments
Show what is available, reserved, deployed and received without confusing one event for another.
Follow the loan
Later phases will cover repayments, support, changes, arrears, closure and understandable statements.
Learn from every phase
Each release will demonstrate a real product decision and the engineering evidence behind it.
06 / The build story
A serious product, developed in understandable steps.
Afzal will use the project to show how an experienced ASP.NET engineer turns a business idea into a dependable application.
Introduce the idea
Explain the vision, people, journey, principles and intended features.
Build applications and review
Demonstrate saved applications, evidence, reviewer ownership and clear status.
Agree and fund
Demonstrate decisions, versioned offers, acceptance and simulated commitments.
Payments, servicing and oversight
Explore reliable payment outcomes, repayments, support, reporting and production foundations.
Every phase will state what is planned, what is working in the demonstration and what evidence has been verified. This keeps the marketing honest while showing the depth of the engineering.
Why follow this project?
See how a senior ASP.NET engineer thinks beyond the screen.
This project is a practical demonstration of product thinking, architecture, C#, ASP.NET Core, Angular, SQL Server, security, reliable workflows and production responsibility. The technology matters because it serves the people and the decisions—not because a framework name is impressive on its own.
ClearLend is fictional, the money is simulated and the commercial model is still being explored. The engineering standards are real.
Explore the local demonstration →