Your existing app
Requirements + examples
Full Core + Late S1,
accepted against Ken’s criteria.
100,000-lead test.
Target: one active closing with Jim.
Rehearsed script and plan,
supported by the deck.

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.
Alex has wealth in his home. He needs breathing room in his monthly budget.

He bought for $300K. His home is now worth $1M. High-interest card debt is squeezing his cash flow.
Illustrative facts supplied for this story. Equity assumes current liens support that estimate. Equity is not an approved borrowing limit.
*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.
You test subjects and messages. Alex sees a relevant invitation, not the data plumbing.
Alex, you recently explored your home’s value. If you’re considering access to some of that equity, you can compare options that keep your existing mortgage in place.
Jim Black can walk through the costs, trade-offs and next step with you.
No obligation to borrow. You can stop follow-up at any time.
Test. Subject, message and call to action.
Learn. Delivery, replies, bookings and attendance.
Respect the stop. Suppression and permission checks stay attached to each lead.
This example does not disclose credit-report contents in email or promise Alex access to all his equity. Sender setup, report access and third-party costs are agreed before live outreach.
You help Alex choose his next step.
Reanna clarifies Alex’s goal and flags missing facts.
Missing facts? Pause calculations, keep talking.
Examples are not confirmed budgets.
Compare combined payments, fees and total cost.
Compare the whole replacement loan’s cost.
No fit? Explain why. Alex can decline borrowing.
Account and credit consent are separate. Saving needs no credit.
No account needed.
Credit consent is separate.
Saving stays available.
Show what changed and why.
Failed or partial data stays unverified. Keep known facts.
Bring this to Jim. The pilot uses his agreed calendar and a human-led handoff.
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.
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.
Requirements + examples
Account → optional credit → saved scenarios + PDF follow Core.
Nov 1–6
Nov 7–20
Nov 21–Dec 4
Nov 7–Dec 11
Dec 12–Jan 8
Dec 12–Jan 8
Core Dec 5–11 · Full Jan 9–22 · Acceptance Jan 23–29
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.
Lower payments can increase total cost.
Like the $30,000 correction: update every affected result.
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.
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.
Jim starts with Alex’s goal and questions. Alex does not start over.
Frank confirms the need, resolves missing details and helps Alex reach the right professional.
Choose a sample time to see what Alex and David receive.
No live booking or notification occurs on this proposal.
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.
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.
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.
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.
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.
A single view from source to conversation, provider follow-up and economics.
No live leads, outreach, credit requests or payments are connected to this illustration. The 100K pool is an input, not a promised conversion count.
Your rehearsed script and fundraising plan, supported by a deck. Investors decide funding.
Nik coaches · David rehearsesStart in November.
Product Show Alex’s choices.
Evidence Separate progress from targets.
Ask What will $2M fund?
Practise the opening, demo, ask and objections.
Investment remains an investor decision.
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.
See what runs in parallel, what depends on what, and where Ken and David review the work.
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.
Sid · Saksham + Megh · Ken + David review
Dependency / checkpoint
Joint planning with Ken and David. Agree scope and acceptance in writing; enables P1 and parallel P3.
Dependency / checkpoint
Requires P0. Leads into P2.
Dependency / checkpoint
Requires P1. Feeds Core checks, P4 and P5.
Dependency / checkpoint
Requires P0. Runs alongside Core / P1 and P2.
Dependency / checkpoint
Requires P1 + P2 and applicable isolation evidence. Core readiness supports customer handoff.
Dependency / checkpoint
Requires P2 + P3, plus provider and consent readiness. Separate from the P5 branch.
Dependency / checkpoint
Requires P2 + P3. No credit dependency.
Dependency / checkpoint
Requires the Core gate + P3–P5; then full review against agreed acceptance.
Dependency / checkpoint
Ken and David review agreed criteria. Proposed handoff by Jan 31; engagement ends at 5 p.m. PT.
Nik + Sid · Sid coordinates · Provider completes
Dependency / checkpoint
Prepare the route, then maintain follow-up. Provider participation and usable leads remain dependencies.
Dependency / checkpoint
Human-led replies, Jim’s meeting if available, customer choice and follow-up. Consent applies.
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.
Nik coaches · David rehearses · Purlend contributes evidence
Dependency / checkpoint
Nov 20 ask checkpoint; Dec 11 script checkpoint. Prepare the story and supporting deck.
Dependency / checkpoint
Dec 18 first rehearsal; Jan 15 refinement. Product and customer evidence informs the work as available, without a closed-deal prerequisite.
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.
The customer must still choose a suitable path, consent and receive provider follow-through.
Use evidence as it becomes available. Rehearsals do not require a completed closing.
These make the demonstration real.
Direct access for six one-hour reviews, approximately every two weeks. Agree his acceptance criteria first, then review working evidence.
Provide the source list, data/report rights, consent records and required licenses. Validate usable volume and permitted channels before outreach.
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.
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.
A delivery team, part-time expertise and focused AI roles. Sid coordinates the engagement; people remain accountable for decisions and delivery.
Delivery teamExecutive direction and fundraising coaching.
Delivery teamEngineering leadership and delivery coordination.
Delivery teamAI engineering and implementation.
Delivery teamAI engineering and implementation.
Part-time and operations support, distinct from the core delivery roles.
Part-timeSpecialist support from another pod.
Specialist support from another pod.
OperationsCoordination and talent continuity.
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.

Turn executive context into clear, decisive communication.
Meet Nikolai ↗
Start sales conversations with a reason the buyer cares about.
Meet Stacy ↗
Turn a research question into a sourced decision brief.
Meet Lex ↗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.
Client perspectives on the team’s work. These are prior engagements, not Purlend results.
“Nik is the C-level whisperer.”

“Thank you for not just replicating, but improving our workflow.”
“clear communication and timely execution”

Up to three sprints · $180K if all begin · $20K discretionary bonus
Review engagement terms ↓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.
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.
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.
Due 15 days after the agreed sprint starts, or receipt if invoiced later. Signing alone creates no fee.
At David Kawata’s sole discretion. Any award and payment occur within 30 days after engagement close.
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.
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.
Framework now; scope agreed before work. Up to three $60,000 monthly sprints. Sprint starts, priorities, deliverables, dependencies, dates and acceptance are agreed in writing. No guaranteed lead count, Pre-Fi access, Jim Black participation, meetings, closing, revenue or capital raise.
Planning interviews include both Ken and David with 100x. Net 15 payment, the cancellation terms above, IP after payment, confidentiality, data protection and the discretionary bonus are set out in proposed agreement v7.1. The engagement ends January 31, 2027 at 5 p.m. PT, without automatic February renewal.
Once signed by both parties, the agreement supersedes prior agreements prospectively while preserving accrued rights and obligations for earlier conduct. The executed agreement controls over this presentation.
DocuSign review draft: created, not sent. Opening this summary does not sign or accept anything. The earlier SOW v1 is historical and is not the current signing packet.
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.
Purlend’s shared ClarityEngine PRD ↗
Alex’s original long-term illustration ↗
The current engagement dates and offer here supersede older presentation dates and commercial examples.
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.