FLIPUR ENTITY
Proposal for Sam and the Flipur team
1 / 19

Flipur Entity · working proposal · September 25, 2026

Four working days with your team. One measurable return.

We are a small company, and we need to learn this market inside your workflow. For two months, we will spend at least two full working days per month with your team while building a source-linked operator review for your five priority counties. You will see the cost, the time returned, and the next decision in numbers.

4 onsite daysAt least 2 per month × 2 months
$6,000Activation and working proof
$300 / monthProduct for 24 months
THE DECISION SAM CAN AUDIT60-day scorecard

Did the workflow earn its cost?

Accepted operator reviewsCounted
Minutes per accepted reviewBefore / after
Data + human costIn dollars
Incremental activationsMeasured, not assumed
We will bring the evidence, the gaps, and the actual math.
Prepared by ServiceAI HQ for Flipur · Private discussion draft.1 / 14

Price · labor · time · proof

Here is the investment and the minimum return it must earn.

Known or proposed numberAmountHow we will use it
Activation, including onsite immersion$6,000Four full days + build and proof
Onsite commitment in first two months4 days · ~32 hoursTwo days/month; 8-hour planning basis
Product, 24 months$300/month · $7,200Access and bounded upkeep
Our proposed fixed two-year price$13,200Plus approved data only

Labor hurdle, conservatively

At an illustrative $25 loaded staff hour, the $550 monthly 24-month equivalent requires 22 hours/month returned. At $50/hour it requires 11 hours/month. Neither rate is a Flipur payroll fact.

Current subscription

Sam reported about $600/month: $14,400 over 24 months if unchanged. Count $0 as retired spend until the invoice, rights and cancellation are confirmed.

Meeting time already invested

Two documented client calls total 58m 47s of recorded meeting time. At $50/hour, that is about $49 per participant, or $147 for three participants as a simple example. It is past investment, not future ROI.

What proves value

Time actual cases before and after; record reviewer corrections, source cash cost and operator activation. Show the day-60 result next to the $6,000 activation and ongoing fee.

Meeting durations: August 28 (33:56) and September 22 (24:51). The $25/$50 rates and eight-hour day are labeled planning assumptions.

September 22 meeting · final discussion

Your question is whether this makes financial sense.

01
What does it replace?

You described a roughly $600 monthly research tool, a Grok bot that searches it, and manual scraping and operator intake. The tool’s full bill and export rights still need checking.

02
What else does it create?

Faster operator onboarding, a complete profile, and a useful next decision. You gave additional operator signups as an example of valuable upside, not a promised result.

03
What is the all-in cost?

You asked for data age and history, refresh burden, source cost, maintenance, scope, timeline, and milestones. A national coverage headline cannot answer that.

Our response: start in the five counties that matter to you, measure one real workflow, and decide expansion from its cost and results.
Source: Sam’s September 22 Entity meeting, about 15:42–22:58. His $600 figure is reported, not an invoice we have verified.2 / 14

How we earn the right to be your provider

Judge us on the operator decision and the ledger behind it.

Work in your process

Observe onboarding with your team, map the actual handoffs, and complete cases with your reviewer. At least two full onsite working days per month for two months are included in activation.

Show the source

Every material finding links to a record and date. Missing EIN, unverified board roles, uncertain entity matches and unavailable project history stay visible.

Publish the scorecard

Show accepted cases, manual minutes, assisted minutes, correction work, data spend, reviewer cost and any conversion change. No invented ROI or automatic decision.

A polished demo may get attention. A repeatable review with known cost is what should earn the contract.
Delivery approach responds to Sam’s request for measurable value, clear milestones and complete operating cost.3 / 14

The current workflow · verify with Flipur in week one

Even with Grok, finding and checking the record takes time.

TodayAsk the operator

Request entity identity, EIN, team, history and recent projects through several handoffs.

TodayResearch again

Use Grok or the current tool to search public records, property activity and court hits for each case; repeat the search when the next question comes.

TodayReconcile by hand

Decide whether names, properties and legal matters belong to the same entity.

TodayMake the call

Summarize the evidence and decide the next onboarding action.

Baseline first: time each step on actual cases, including Grok-assisted research, requests, waiting, correction, tool fees and human review. The product should retrieve an indexed, cited result quickly, then let Grok query the approved record once an interface is built. We will count only time actually removed from an accepted review.
Sam described today’s Grok-plus-tool workflow on September 22. Search speed and hours saved must be timed on real cases; the client bot API is not live.4 / 14

What the first activation buys

From entity name to a reviewed next action.

ACCEPTANCE RECORD · STRUCTURE, NOT A LIVE OPERATOROne Flipur operator dossier
Entity, standing, EINSource or authorized intake
People and actual rolesNamed evidence and dates
Prior projectsClaim vs recorded match
Property and transfer historyCounty-qualified
LitigationIdentity, role, status
Unresolved fieldsShown explicitly
Human-reviewed internal grade → separate fee, privilege and promotion scenarios → next action.

The acceptance test

Select one consented operator, run intake to decision with a Flipur reviewer, retain source links and exceptions, then repeat the process on a second case. Record total elapsed time, hands-on minutes and corrections for both.

Success is a usable decision, not a count of scraped rows or a score generated without review.
EIN and board membership may require operator-provided records. Recorded price spread is not profit.5 / 14

Product proof · status as of September 25 review

There is a working foundation. We still have acceptance work.

PRIVATE CODE · STAFF TEST PENDING

Review workflow

  • Entity intake, claims and reconciliation
  • Litigation queue and internal grade preview
  • Fee, privilege and promotion previews
  • Cases, assignment, exports and time tracking
NEXT ACCEPTANCE GATES

Real operation

  • Flipur staff sign-in and reviewer test
  • Complete five-county field/year ledger
  • Repeatable 24-month history where rights permit
  • Named investor-tool integration and bot API
Commitment: we will mark each acceptance item passed, partial, or blocked on the 60-day scorecard. Existing code does not equal a finished Flipur workflow.
Current delivery matrix lists 38 proposed outcomes and zero fully accepted end-to-end. It is a roadmap, not contracted scope.6 / 14

Feature inventory · evidence from current delivery matrix

Research and evidence features already have a working base.

CapabilityCurrent stateValue in Sam’s workflow
Entity, person, address and property searchPublic partialStart from one entity or place
Map, parcel and geographic source coveragePublic partialSee where records exist
Officer/manager graph and aliasesPublic / private partialFind roles to verify
Deed, transfer and recorded sale contextPilot / public partialCheck claimed projects
Litigation candidates and reviewer queuePublic partialSurface cases for role review
Property, permit, lender, lien and hazard contextPublic partialPut risk signals in one view
Important limit: “working base” means these screens and data paths exist. Names, sale pairs and case hits need source and identity checks before they are used in an operator decision.
Source: September 23 feature matrix and delivery state. Partial coverage is labeled; no five-county history is implied.

Feature inventory · built in private, still to be accepted

The operator workflow Sam asked for is taking shape.

CapabilityCurrent stateAcceptance we need
Entity-name intake, formation and standingPrivate, unverifiedOne real staff case
Claims intake and claim-to-record reconciliationPrivate, unverifiedReviewer accepts matches
Purchase/resale timeline, gross spread, hold periodPrivate, boundedQualified sale pairs
Internal grade, override and decision logPrivate, unverifiedApproved policy and audit
Fee, privilege and promotion previewsPrivate, unverifiedHuman policy sign-off
Evidence requests, memo, assignments and exportPrivate, unverifiedReal sign-in and review
Onboarding funnel and time/unit-cost dashboardPrivate, boundedObserved case data
What $6,000 activates: complete the first and repeat case through this workflow, fix the handoffs, and record what still requires a person or licensed source.
Private configured code is not yet a fully accepted Flipur staff workflow. No automated grade or live fee change is promised.

Roadmap tied to a business outcome

Build the next feature when its value and data rights are known.

Feature laneCurrent positionValue test
Buyer discovery by county, ZIP, project, property and datePartial componentsQualified buyers per search
Buy boxes, portfolio and deal-to-buyer matchingPrivate, unverifiedUseful matches and responses
Permitted contact enrichmentManual / rights gateCost per usable contact
Distress, probate/inherited, lien and sale signalsPublic partial / pilotQualified lead per source dollar
Recurring alerts and analyst watchlistsOpen / private partialTime to a reviewed change
Grok/API access and investor-tool integrationOpenMinutes removed per repeated query
Sequence: first accept operator onboarding and its data economics. Then choose the buyer, lead or API lane with the highest measured return and a separate scope.
These are proposed outcomes, not features included in the first $6,000 milestone unless explicitly named in the signed scope.

Where we start

Prioritize your five counties. Price the records before buying them.

OrangeFirst case and historical-source priority
Los AngelesSeparate city and county coverage
RiversideVerify file scope and rights
San BernardinoMeasure party and sale fields
San DiegoCheck history and refresh options
Existing Flipur source coverage dashboard
Current source ledger. Row counts are not complete two-year named histories.

One source ledger per county

For each field: available period, name coverage, purchase/sale qualification, record age, acquisition time, refresh schedule, license rights, cash price and maintenance effort.

Compare free public sources, targeted county files and a licensed provider. We will present the 24-month option and its exact incremental cost before any paid purchase.

Orange County’s previously found $77/week index price concerns a specific forward feed; it does not quote a two-year backfill.7 / 14

Financial discipline

The $300 fee is not the whole operating cost.

Cost lineProposed amountStatus
Activation · workflow, source ledger, four onsite working days$6,000 onceQuoted here
Product · access, ordinary hosting and bounded upkeep$300 / monthQuoted here
Paid county data / API / enrichmentUnknownEstimate and approve first
Flipur reviewer timeMeasured hours × rateBaseline and pilot
Ongoing onsite service after day 60Separate scopeOptional
Proposed fixed 24-month product price$13,200Plus approved extras
Data example: the previously identified Orange County weekly index was $77/week, about $4,004/year if purchased every week. We have not confirmed the current quote, historical backfill, rights or need for that feed. It is not included in $13,200.
We will compare total annual cost, including human review, with the present tool after receiving its plan, invoice and export terms.8 / 14

How the investment pays back

Four measurable value lines. Count each only once.

A
Reviewer capacity returned

Accepted reviews per month × hands-on minutes removed ÷ 60 × loaded reviewer rate. This is capacity, not cash saved unless it avoids spending or is used productively.

B
Actual spend retired

Count the existing research subscription only if Flipur cancels it. Count export upgrades or contractor spend only when documented and discontinued.

C
Incremental operator contribution

New activated operators attributable to faster review × measured contribution per operator. Signups alone are not revenue; compare to a baseline.

D
All incremental costs

Subtract our fee, approved data/API purchases, added infrastructure, review time and any continuing outside tools.

At day 60 we will show observations and a range. We cannot responsibly promise ten extra operators or a fixed dollar return now.9 / 14

The threshold before upside

At $50 per reviewer hour, 11 hours a month covers the fixed two-year average.

24-MONTH PRODUCT MATH
$13,200

$6,000 activation + 24 × $300


$550 / month equivalent

$550 ÷ illustrative $50 loaded hourly rate = 11 hours / month of capacity. In year one, the actual cash outlay is $9,600, or $800 per month equivalent.

Translate that into real cases

Accepted reviews / monthMinutes saved / reviewValue at $50 / hr
1030$250 / month
2030$500 / month
2230$550 / month
3030$750 / month

Illustrations only. Zero canceled subscriptions, zero operator-contribution upside and zero extra data cost assumed. Every $100/month of added data raises this threshold by two hours at $50/hour.

Capacity is not a booked saving. Validate volume, minutes, staff cost and data charges before claiming ROI.10 / 14

Illustrative economics · replace with Flipur’s observed inputs

What volume and time reduction would justify the price?

Monthly scenario at $50 / reviewer hourReturned capacityVs $550/month fixed average
10 reviews × 30 minutes removed5 hours · $250$300 below
20 reviews × 45 minutes removed15 hours · $750$200 above
30 reviews × 45 minutes removed22.5 hours · $1,125$575 above

Cash spend test

If the $600/month tool stays, avoided subscription spend is $0. If it is retired, confirm the cancellation date and feature coverage before crediting savings.

Operator upside test

For each additional activated operator attributable to faster onboarding, use Flipur’s actual contribution after servicing cost. No conversion or margin is assumed here.

Data sensitivity

Each $100/month in approved source spend requires two more reviewer hours at the illustrated $50/hour rate, unless it produces other measured value.

Year-one hurdle

$9,600 in first-year cash payments equals $800/month. At $50/hour, time value alone needs 16 hours/month in year one before extra data.

These are scenarios, not forecasts. Capacity value, retired cash spend and incremental operator contribution are separate lines.

Implementation and proof

Four onsite days. Two real cases. One decision on the numbers.

Weeks 1–2 · observe and baseline

Choose the first operator; inventory the current subscription, intake steps, staff minutes and source permissions. Confirm the five-county priority and acceptance checklist.

Weeks 3–4 · complete case one

Run entity intake, evidence, project and litigation review; record exceptions and a human next action. Reconcile source cash costs.

Weeks 5–6 · repeat case two

Fix handoffs; time the second review; test a permitted export or integration path after the existing tool and rights are identified.

Weeks 7–8 · cost and acceptance review

Present before/after minutes, source ledger, total cost, product gaps, and an agreed go/adjust/stop recommendation.

ONSITE WORK
Two full days each month

At least two onsite working days per month for the first two months, at an agreed local site. Planning basis: one lead, eight hours per day, 32 onsite hours total. Sam and Adrian do not need to attend all day; we shadow the real workflow, work with staff, and return a short decision list.


The exact dates, location, access, travel boundary and named reviewer go into the signed scope. Offsite build work is also part of activation.

Dates start when the first case, access and data permissions are ready. Unavailable paid sources remain visible as scope gaps.11 / 14

Use the incumbent as context, not a promised saving

The proposal is $13,200 fixed over two years.

Base subscription comparisonFirst 12 months24 months
Reported current tool · $600/month$7,200$14,400
Flipur Entity · $6,000 + $300/month$9,600$13,200
Fixed-price difference+$2,400 first year−$1,200 over 24 months

If the old tool stays

The subscriptions stack: $27,600 over 24 months before paid data and labor. In that case value must come from faster reviews or new contribution, not replacement savings.

If it can be retired

Confirm its contract, export and features first. The $1,200 fixed-price gap is small; the stronger case is a reusable onboarding decision and less manual work.

Sam reported $600/month, possibly with upgraded downloads. No invoice, cancellation date or equivalent feature comparison has been verified.12 / 14

Scope and continuity

Own the decision. Know the boundaries.

Included in $6,000

First/repeat operator review, four full onsite working days in 60 days, five-county source ledger, baseline and value scorecard, and a bounded integration assessment.

Included in $300/month

Product access, ordinary hosting, maintenance, agreed source refresh operation and bounded support. We will define support response and use limits in the scope.

Approved separately

New paid data, API/enrichment fees, unusual infrastructure, ongoing twice-monthly onsite work, broad buyer/lead feeds, CRM replacement and bot API integration.

Flipur control

Flipur controls its case data, reviewer decisions and approved exports. We document backups and transition. Exclusive IP or code buyout needs a separate agreement.

Decision safeguards

Internal grade only. Human approval for fee, privilege and promotion changes. No automatic outreach, public adverse label or live charge change.

Expansion rule

After the first workflow is accepted, price additional counties, source depth, buyer discovery or integrations against the measured benefit and actual rights.

Discussion terms; support limits, data budget, payment timing, rights and exit mechanics belong in the final agreement.13 / 14

Our recommendation

Invest in one measurable workflow. Expand when its value is visible.

We propose $6,000 to work inside Flipur’s niche for at least two full onsite days per month over two months, implement Entity around a real operator review, and prove the value. The $300 monthly product fee keeps the accepted workflow operating. At day 60, you receive a repeat case, a county-by-county cost ledger and a financial scorecard.

Choose the first operatorReview the current tool’s actual billBook four onsite working daysApprove source purchases only after quotes
$6,000 activation + $300/month · $13,200 fixed over 24 months.