This study accepts strong inbound cases. Paid interviews are currently focused on the three active studies.

Study for fintech and vertical SaaS product teams

Which provider record should your product treat as commercial truth?

This study resolves one active ambiguity in provider data that is blocking a customer workflow, financial decision, or release. It produces an evidence contract and test corpus, not a general integration engagement.

Apply with a failing case See the fixed scope

The behavior being examined

A real event comes before an offer.

Apply if your team currently has:

A provider payload whose economic meaning is ambiguous or undocumented.
Conflicting order, payment, subscription, refund, payout, or accounting records.
A customer workflow blocked by missing provider semantics.
Engineering time already allocated to the problem.
A downstream decision that becomes wrong if the record is interpreted badly.

Roadmap curiosity and requests for generic connectors are not sufficient.

Not a fit

No active customer or roadmap blocker.
No real payload or reproducible failure.
Request is simply to add another connector.
Generic architecture advice without an accountable product owner.
No engineering or budget commitment.

Fixed scope offer

Commercial Data Resolution Sprint

$5,000

For one provider, object family, and downstream decision, the sprint produces:

01A hierarchy of available evidence sources.
02Explicit commercial semantics for relevant fields and states.
03A normalized output contract with provenance and unresolved states.
04A redacted fixture corpus covering observed edge cases.
05Acceptance tests that do not depend on a specific implementation.
06A memo stating what can and cannot be safely promised downstream.

A budgeted design partnership may substitute when procurement cannot complete in the study window. The sprint does not build or maintain the production connector.

Minimum data

The smallest evidence set that can answer the question.

Normally required:

Redacted real payloads for failing and expected cases.
Provider documentation and current integration behavior.
The existing normalization or business rule.
The downstream customer claim or product decision.
Access to the product or engineering owner for two working sessions.

Only one provider, object family, and downstream decision are in scope.

What happens after delivery

The artifact is not the outcome.

Thirty days later, I ask whether the contract entered implementation, changed a product claim, prevented a release, or was replaced by an existing vendor or provider capability.

Application

Tell me about the decision you’re working through

Takes approximately 4–6 minutes. Do not submit credentials or raw data.

I'll review the decision, who owns it, and whether the available records can answer the question.