100xPurlend

Your next three months.

100xPurlend
100xPurlend · November 1, 2026 – January 31, 2027

Three outcomes. One team.

01 / Product

Deliver the MVP.

Full Core + Late S1,
accepted against Ken’s criteria.

02 / Customers

Prove the path to closing.

100,000-lead test.
Target: one active closing with Jim.

03 / Fundraising

Prepare the next raise.

Rehearsed script and plan,
supported by the deck.

Alex’s illustrative Irvine home, retained from the original story
Alex’s next move.
Your app→Alex’s choices
Human conversations→A suitable deal
Prepare your raise→Rehearsed pitch

Complete your MVP. Test the full path. Prepare your next raise.

Follow Alex’s story ↓

Proposed engagement. The screens below are interactive illustrations. Providers decide credit and complete loans; investors decide funding.

01 / The starting point

A home-value inquiry.
A reason to act.

Alex has wealth in his home. He needs breathing room in his monthly budget.

Illustrative Irvine home for Alex’s example
Irvine, California · Illustrative homeowner

Meet Alex.

He bought for $300K. His home is now worth $1M. High-interest card debt is squeezing his cash flow.

Home value$1M
Estimated equity$700K+
Credit-card debt$100K24.99% APR

Illustrative facts supplied for this story. Equity assumes current liens support that estimate. Equity is not an approved borrowing limit.

01 · AcquisitionKelley Blue Book HomesHome-value lead source*
↓
02 · Data + permission recordPreFi reportsUse only data authorized for this purpose.
↓
03 · EngagementReannaA relevant email. A clear next step.

*Proposed source based on the call. David confirms the partner, report rights and permissions for the 100,000-lead test. Credit data requires its own valid authorization.

100,000-lead testValidate the list → Test in batches → Learn from replies → Expand what works
02 / Reanna earns the reply

One useful email.
A human at the next step.

You test subjects and messages. Alex sees a relevant invitation, not the data plumbing.

03 / Alex’s decision

Give Alex a reason to respond.

You help Alex choose his next step.

Email→Reanna clarifies→Alex compares→Optional account + credit→Save→Frank + Jim
S1 Core · No account needed

“Can I manage debt and keep my mortgage rate?”

Reanna clarifies Alex’s goal and flags missing facts.

purlendCore
Alex’s goal
AlexI need to manage debt.
ReannaWhat matters most: payments, total cost or keeping your mortgage?
Property facts Source + dateRequested cash Not yet chosen

Missing facts? Pause calculations, keep talking.

Core ends with clarity.Then: return, optional credit, save.
Late S1

Return on your terms.

Account and credit consent are separate. Saving needs no credit.

purlendLate S1
Return securely

Come back later?

Not now

Continue Core

No account needed.

Create an account

Secure sign-in + MFA

Credit consent is separate.

Scope and experience checks

Full Core + Late S1 stays included

Core: Arrive, Address, Converse, Explore, Clarity. Late S1: Account, Verify, Refine, Save. Property/source data, recovery, access controls, MFA, tenant separation, supported credit refinement and saved scenarios/PDF remain part of the plan.

Checks to agree with you

Unknown is not zero. Corrections update affected results together. No fit remains a valid outcome. Account and credit consent remain separate. Saved view and PDF use the same selected result. Provider errors preserve known facts.

One-time soft credit is not a lender quote or approval. Rich reports, recurring monitoring and automated marketplace fulfilment remain later features.

04 / Finish your MVP

Build on what you have.

Reuse

Your existing app

Requirements + examples

Complete
CLR-6Understand the goal.
CLR-7Guide the conversation.
CLR-5Calculate the options.
CLR-9Explain the options.

Account → optional credit → saved scenarios + PDF follow Core.

Prove

Testing + Purlend review

Full Core + Late S1,
accepted against Ken’s criteria.
Explore CLR-6 ↗
Delivery work packets

P0 · Agree what ready means

Nov 1–6

Reuse
PRD, rules and reviewed examples.
Complete
Match current app versions and agree criteria with Purlend.
Prove
Expected results, reviewers and release evidence agreed.

P1 · Understand and correct

Nov 7–20

Reuse
Code-owned conversation controller.
Complete
Goal meaning, fact updates, missing-data recovery.
Prove
Sample amounts stay examples; corrections reach every affected result.

P2 · Make numbers and cards agree

Nov 21–Dec 4

Reuse
Calculation helpers and scenario cards.
Complete
Current-result links, totals, fees and payment labels.
Prove
Domain-reviewed fixtures, neutral comparisons and no-fit cases.

P3 · Let Alex return securely

Nov 7–Dec 11

Reuse
Account routes and ownership controls.
Complete
MFA, recovery and account/session binding.
Prove
Secure return, cross-user denial and separate credit choice.

P4 · Credit and refinement

Dec 12–Jan 8

Reuse
P2 calculations and P3 access.
Complete
One agreed provider, consent and supported fact updates.
Prove
Decline, timeout, partial data and duplicate-request handling.

P5 · Save and export

Dec 12–Jan 8

Reuse
Existing storage and export paths.
Complete
Saved scenario return and matching PDF.
Prove
Same selected facts in view and PDF; no credit required.

P6 · Prove the complete experience

Core Dec 5–11 · Full Jan 9–22 · Acceptance Jan 23–29

Reuse
Existing tests and release setup.
Complete
Integrated checks, recovery, accessibility and handoff.
Prove
Core gate with isolation evidence, then full Core + Late review with Purlend.

These are delivery checks to agree and execute, not claims of passed tests. Shared correction, calculation and account foundations are counted once. Selected code and historical examples guide reuse; live readiness is established through the agreed checks.

05 / A clear requirement

Clarify “save money.”

  1. Need“Save money.”
  2. ClarifyPayment or interest?
  3. ConfirmUpdate the comparison.
  4. TestCorrect the goal; check affected results.
purlendTry Alex’s choice
Reanna → AlexWhat matters most, Alex?
Alex confirms

Lower monthly payment

Compare combined monthly payments+Term + total cost

Lower payments can increase total cost.

Like the $30,000 correction: update every affected result.

CLR-6 requirement + test

From meaning to behaviour

Given an ambiguous “save money” goal, ask for clarification before treating it as confirmed. Apply the answer to the question asked. Keep source and confirmation status. When Alex corrects the goal, replace the current meaning and refresh dependent explanations and options using ready inputs.

A $30,000 illustration remains separate from requested cash. Missing required inputs hold affected calculations; conversation can continue.

Acceptance example

Given monthly-payment priority, the comparison shows combined payments alongside term and total cost. When Alex corrects to total-interest priority, the confirmed goal and comparison emphasis change together. No obsolete explanation remains. Numeric results are recalculated only where the changed input affects them.

This is an illustrative acceptance case grounded in CLR-6/7 and the baseline correction example. Confirm governing child-story wording and expected fixtures in P0. The controls here demonstrate the requirement, not Purlend’s implementation.

06 / The human handoff

Alex books.
Frank keeps the context.

Jim starts with Alex’s goal and questions. Alex does not start over.

FFrankIllustrative call-center repHuman follow-up

Ready for Jim’s call.

  • Alex’s goalReduce high-interest debt
  • ProtectHis existing first mortgage
  • Open questionSecond-lien cost and affordability
  • PermissionSMS not authorized

Frank confirms the need, resolves missing details and helps Alex reach the right professional.

Email confirmation only. No automated text is sent.

Jim Black · AppointmentSimulated booking
Alex’s next step

Talk through your
home-equity options.

Choose a sample time to see what Alex and David receive.

Example appointment10:00 a.m. PTJim’s real calendar connects after his approval.

No live booking or notification occurs on this proposal.

The decision stays with Alex

Stay. Sell. Or pause.

Explore a second lien with Jim.

Compare the combined payments, fees, term and total cost. Keep the first mortgage if a suitable second lien fits. The provider decides eligibility and terms.

Reanna’s follow-through

“Here’s what we discussed.”

Your next step: Jim reviews a suitable second-lien option.

Your questions: Costs, payment, required documents and alternatives.

What happens next: A named person follows up. Alex can correct the recap.

The call becomes
the next action.

With participant approval, use Roam or a Pocket recording to prepare the recap. Share through the approved channel. Keep the source, decisions and follow-up together.

Recording is optional. Without approval, use human notes. Call capture and recap delivery are pilot operations, not an expansion of the agreed S1 product.

Jim’s agreement and the pilot boundary

Provider readiness

Confirm Jim’s calendar, availability, lead acceptance, follow-up SLA, recording/recap permissions and provider route. Jim advises; the lender owns underwriting and completion. Frank is a representative role, with the named operator to be confirmed.

Proposed model: $100 per phone call. Jim must agree the payable event, service, price and cancellation/no-show handling in writing. No revenue is earned by the example shown here.

Separate options

Voice-AI cold calling with Kastle or Flair Labs is a separately priced option, outside this engagement. Automated SMS is excluded without explicit authorization. No loan is required to make this a valid customer interaction.

The commercial arrangement must be reviewed for applicable referral and marketing-payment rules before activation. This proposal does not establish that a per-call fee is permissible.

07 / David’s operating view

See the handoffs.
Know what happens next.

A single view from source to conversation, provider follow-up and economics.

Purlend · Pilot oversightIllustrative operating view
Test pool100,000Rights + usability to validate
Target≥ 1Lead actively closing with Jim
Proposed commercial model$100 / callAgreement + payable event pending
AAlex · IrvineJim review
Source + permissionHome-value inquiryEmail only · SMS off
Appointment10:00 a.m. PTFrank owns follow-up
Customer’s next actionExplore a second lienProvider review pending

No live leads, outreach, credit requests or payments are connected to this illustration. The 100K pool is an input, not a promised conversion count.

08 / Prepare the next $2M round

Rehearse your next raise.

Your rehearsed script and fundraising plan, supported by a deck. Investors decide funding.

Nik coaches · David rehearses

Start in November.

Product progress+Customer evidence→Your pitch
purlendYour fundraising outputs
Script outline

“Clarity before choosing a product.”

Product Show Alex’s choices.

Evidence Separate progress from targets.

Ask What will $2M fund?

ProblemDemoEvidenceMilestones
Deck supports the script.
Fundraising work plan

Nik works with David and your team on the narrative, supporting deck, raise purpose, use of funds and milestones. Coaching covers delivery and objections, with rehearsals and revisions. The plan identifies investor fit, approach order, preparation and follow-up ownership. Product and customer evidence enter as available; a completed deal is not a prerequisite to starting preparation. No investment commitment, completed introduction or existing signed provider agreement is claimed.

09 / The proposed roadmap

Three workstreams.
One clear view.

See what runs in parallel, what depends on what, and where Ken and David review the work.

Illustrative planning windows, not delivery commitments.

Ken, David and 100x agree scope, deliverables, dependencies, dates and acceptance in writing before work starts. Leads, Pre-Fi access, partner participation, meetings and commercial outcomes are not guaranteed.

15 work windows · 3 workstreams
Work window
November 2026December 2026January 2027
Dates
01

Build and validate the MVP

Sid · Saksham + Megh · Ken + David review

P0Agree acceptanceNov 1–6

Dependency / checkpoint
Joint planning with Ken and David. Agree scope and acceptance in writing; enables P1 and parallel P3.

Read phase details and ticket context ↗
P1Understand + correctNov 7–20

Dependency / checkpoint
Requires P0. Leads into P2.

Read phase details and ticket context ↗
P2Calculations + cardsNov 21–Dec 4

Dependency / checkpoint
Requires P1. Feeds Core checks, P4 and P5.

Read phase details and ticket context ↗
P3Secure returnNov 7–Dec 11

Dependency / checkpoint
Requires P0. Runs alongside Core / P1 and P2.

Read phase details and ticket context ↗
P6Core checksDec 5–11

Dependency / checkpoint
Requires P1 + P2 and applicable isolation evidence. Core readiness supports customer handoff.

Read phase details and ticket context ↗
P4Credit + refineDec 12–Jan 8

Dependency / checkpoint
Requires P2 + P3, plus provider and consent readiness. Separate from the P5 branch.

Read phase details and ticket context ↗
P5Save + PDFDec 12–Jan 8

Dependency / checkpoint
Requires P2 + P3. No credit dependency.

Read phase details and ticket context ↗
P6Full MVP checksJan 9–22

Dependency / checkpoint
Requires the Core gate + P3–P5; then full review against agreed acceptance.

Read phase details and ticket context ↗
ReviewPurlend review + acceptanceJan 23–29

Dependency / checkpoint
Ken and David review agreed criteria. Proposed handoff by Jan 31; engagement ends at 5 p.m. PT.

02

Validate the customer journey

Nik + Sid · Sid coordinates · Provider completes

PrepareOutreach + provider routeNov 1–13

Dependency / checkpoint
Prepare the route, then maintain follow-up. Provider participation and usable leads remain dependencies.

ConnectCustomer conversationsNov 16 onward

Dependency / checkpoint
Human-led replies, Jim’s meeting if available, customer choice and follow-up. Consent applies.

HandoffMVP-assisted handoff → completionDec 18–Jan 29

Dependency / checkpoint
Dec 18 handoff checkpoint; Jan 29 active-closing target. Requires ready Core, suitable customer choice, consent and provider follow-through. A closing is not guaranteed.

03

Prepare the next raise

Nik coaches · David rehearses · Purlend contributes evidence

StoryEvidence + script + deckNov 1–Dec 11

Dependency / checkpoint
Nov 20 ask checkpoint; Dec 11 script checkpoint. Prepare the story and supporting deck.

PracticeCoach, rehearse + refineDec 18–Jan 15

Dependency / checkpoint
Dec 18 first rehearsal; Jan 15 refinement. Product and customer evidence informs the work as available, without a closed-deal prerequisite.

PlanFundraising plan + final evidenceJan 22–29

Dependency / checkpoint
Jan 22 plan checkpoint; Jan 29 evidence refresh. Raising capital is not guaranteed.

Select a work window to see its prerequisites and checkpoints. Bars show proposed duration, not progress.

Product → Customer journey

Core readiness enables handoff.

The customer must still choose a suitable path, consent and receive provider follow-through.

Product + Customer evidence → Fundraising

Evidence strengthens the story.

Use evidence as it becomes available. Rehearsals do not require a completed closing.

10 / What you provide

Three inputs.
One accountable plan.

These make the demonstration real.

01

Six hours with Ken.

Direct access for six one-hour reviews, approximately every two weeks. Agree his acceptance criteria first, then review working evidence.

02

100,000 leads + usable PreFi reports.

Provide the source list, data/report rights, consent records and required licenses. Validate usable volume and permitted channels before outreach.

03

Jim’s calendar + operating agreement.

Approve the calendar, lead acceptance, follow-up SLA and $100-per-call proposal. Agree Roam/Pocket recording and recap permissions, with a human-notes fallback.

Product access, costs and decision owners

GitHub/Jira access for Nik, Sid, Saksham, Megh and Bhumika, plus the existing app, current requirements and relevant environments. David/Sydney own product clarification and review. Ken owns the agreed acceptance decision. Sid owns delivery coordination.

Purlend supplies lead/report licenses and provider arrangements. Third-party spend requires separate approval. Scope changes are agreed explicitly; they do not silently extend the January 31 engagement.

The people behind the work

Human judgment.
AI capacity.

A delivery team, part-time expertise and focused AI roles. Sid coordinates the engagement; people remain accountable for decisions and delivery.

Nik ShahDelivery team

Nik Shah

Founder & CEO

Executive direction and fundraising coaching.

Sid SamantDelivery team

Sid Samant

Engagement lead

Engineering leadership and delivery coordination.

Saksham JainDelivery team

Saksham Jain

AI engineer

AI engineering and implementation.

Megh LeenaDelivery team

Megh Leena

AI engineer

AI engineering and implementation.

Specialists when the work needs them.

Part-time and operations support, distinct from the core delivery roles.

HarshmeetPart-time

Harshmeet

Part-time expert

Specialist support from another pod.

SS
Part-time

Sushant

Part-time expert

Specialist support from another pod.

Bhumika PrasadOperations

Bhumika Prasad

Operations support

Coordination and talent continuity.

Three focused AI teammates.

Proposed engagement roles using the public Website v6 profiles. AI output supports the team’s work; it does not replace human review or authorize outreach.

Nikolai, generated portrait of an AI persona
AI persona

Nikolai

Conversational intelligence

Turn executive context into clear, decisive communication.

Meet Nikolai ↗
Stacy, generated portrait of an AI persona
AI persona

Stacy

SDR automation

Start sales conversations with a reason the buyer cares about.

Meet Stacy ↗
Lex, generated portrait of an AI persona
AI persona

Lex

Housing market insights

Turn a research question into a sourced decision brief.

Meet Lex ↗
Staffing and advisor context

Staffing, availability and allocation are agreed in writing. Part-time experts and AI personas are not additional full-time delivery commitments. UI/UX expertise is available as needed.

Advisor perspective: Alex Urmersbach, former Kiavi CFO; Roger Park, former EY AI and innovation leader; Brian May, former EY financial services consulting leader. Advisor perspective is separate from delivery staffing.

Human portraits and public profile descriptions are sourced from Website v6. AI portraits are generated representations. Sushant’s portrait is pending verification.

From the public 100x website

How clients describe
working with us.

Client perspectives on the team’s work. These are prior engagements, not Purlend results.

Discovery workshop
“Nik is the C-level whisperer.”
Alysse Prosnick
Alysse ProsnickEVP Operations · Angel Oak Mortgage Solutions
Role at time of testimonial
“Thank you for not just replicating, but improving our workflow.”
Laura Guilbert
Laura GuilbertOperations Lead · Mainstay
Excerpt · Role at time of testimonial
“clear communication and timely execution”
Marcel Bock
Marcel BockCEO · Enerclave
Read the public testimonials ↗
11 / The engagement

Your three-month engagement.

Proposed engagement fee$60K/ month

Up to three sprints · $180K if all begin · $20K discretionary bonus

Review engagement terms ↓
What Purlend gets

Your IP. Clear protections.

  • IP rights in deliverables after the relevant sprint is paid.
  • Non-disclosure, with the testimonial exception below, and non-solicitation terms.
  • Data-protection obligations in the final agreement.
What Purlend won’t get

Final delivery authority.

Final decisions on code and design and timelines will be by 100x, not Purlend.

Purlend supplies business requirements. Ken, David and 100x agree scope and acceptance in writing.

Testimonial rights

100x can publish your testimonials.

Testimonials provided by Purlend or its authorized representatives are excluded from non-disclosure restrictions. 100x may use them across all public-facing materials without further approval.

Read the testimonial exception

Testimonials about 100x’s services provided by Purlend or its authorized representatives are excluded from Confidential Information and the agreement’s non-disclosure restrictions. Purlend permits 100x to reproduce, publish, distribute and display these testimonials, with accurate attribution, in any public-facing medium, including websites, social media, proposals, presentations, case studies, marketing materials and public knowledge bases, during and after the engagement, without further approval or payment.

100x may edit testimonials for length or formatting without changing their meaning. This exception does not permit disclosure of borrower data, unrelated confidential information or private correspondence that was not provided as a testimonial.

Per monthly sprint · Net 15$60,000

Due 15 days after the agreed sprint starts, or receipt if invoiced later. Signing alone creates no fee.

Discretionary closing bonus$20,000

At David Kawata’s sole discretion. Any award and payment occur within 30 days after engagement close.

Low-friction exit7 days’ notice

Either party may cancel at least 7 calendar days before the next confirmed sprint. Later notice applies after that sprint unless agreed otherwise.

Overdue undisputed principal: 1% per month simple interest (12% nominal annual), calculated daily on actual/365 from the day after the due date, capped by law; no compounding. Good-faith disputed amounts are due 5 business days after resolution.

Agreement + e-sign

Proposed services agreement v7.1.

Scope is agreed later in writing before work starts. DocuSign is the intended signing provider; the current review draft has not been sent.

Signature submission remains paused for Nik’s review. This page is a proposal summary, not a signature request.

Review proposed terms ↓
Proposed agreement term

One agreement governs the engagement.

Once signed by both parties, proposed agreement v7.1 supersedes previous agreements prospectively, preserving accrued rights and obligations relating to earlier conduct. It sets out IP, confidentiality, staff protection and data-protection terms.

These are proposed terms until execution. Publishing or opening this page does not replace an existing signed agreement.

Next step

Agree the terms. Confirm the first sprint.

Review the proposed services agreement with 100x. Start dates are agreed in writing. Engagement ends at 5:00 p.m. PT on Sunday, January 31, 2027.

Sources + scope notes

What this proposal builds on

Purlend’s shared ClarityEngine PRD ↗

Alex’s original long-term illustration ↗

Engagement terms above ↑

The current engagement dates and offer here supersede older presentation dates and commercial examples.

How to read the evidence

Six saved scenarios were reviewed: 1, 2, 3, 5, 6 and 7. They inform examples; they are not blanket approval of demonstrated behaviour.

Historical June/July findings inform the approach, not assertions that those defects remain today. This page offers future delivery work and does not certify current functionality or production tests.

The Alex illustration carries forward the original story’s home. No refinance figures, commissions or future sale are presented as results of this second-lien pilot.