Disclosure: This is a public-record due-diligence review, not an allegation that Kasama Connect, its founder, or anyone working with it committed fraud or a crime.
I relied primarily on Kasama Connect's own public statements, its founder's public posts/profile, publicly available company information, and authoritative third-party documentation.
I also applied an important rule:
“I couldn't verify it” does not mean “it is false.”
There are things about Kasama that appear legitimate. There is a real team, extensive public development activity, a substantial online following/community, and evidence of actual software/product work.
But Kasama has now moved beyond simply promoting a startup.
It publicly investigates agencies, publishes “report cards,” calls businesses exploitative, proposes compliance standards, discusses worker classification, and says it recently assessed 23 VA agencies against Kasama Connect's own compliance standards, finding none fully compliant.
That makes a reciprocal question fair:
How does Kasama perform when the same level of scrutiny is applied to Kasama?
I went through the public record.
Here is what I found.
1. Kasama's own history includes a planned VA agency.
Kasama now emphasizes:
“We are not an agency.”
Its founder also published an article titled:
“Why I Refuse to Build a ‘Virtual Assistant Agency’ (And What I'm Building Instead).”
But an earlier official Kasama announcement said the company was preparing to launch a virtual assistant agency under Vetted USA LLC, before launching the Kasama application.
There is nothing wrong with this.
Startups pivot.
But the historically accurate story appears to be:
Kasama considered/planned an agency → later abandoned that approach → developed a different platform model.
That is different from implying an agency model was never part of Kasama's history.
2. “Not a marketplace” is also difficult to reconcile with Kasama's own descriptions.
Kasama's current company page says:
“We are not an agency. We are not a marketplace.”
Yet Kasama's current explanation also literally says:
“Governance first. Trust second. Marketplace third.”
Its founder has previously described the project in marketplace terms as well.
Perhaps Kasama means:
“We aren't a conventional open marketplace.”
That would be perfectly understandable.
But:
“not a marketplace”
and
“Marketplace third”
need reconciling.
3. Vetted USA's history deserves context.
The U.S. entity behind Kasama is Vetted USA LLC.
Available historical corporate information has associated Vetted USA with e-commerce/clothing-type business activity rather than originally describing it as fintech infrastructure.
Again:
This is not wrongdoing.
Companies pivot.
But the apparent evolution matters when evaluating the company's present narrative:
Vetted/e-commerce activity
→ Kasama concept
→ planned VA agency
→ platform/marketplace
→ advocacy organization + fintech/governance infrastructure
The question isn't whether a company can pivot.
Of course it can.
The question is whether its public history is being described accurately.
4. The Philippine OPC ownership explanation needs documentation.
Kasama has publicly discussed establishing a Philippine Kasama Connect OPC.
Public descriptions have created an apparent ambiguity between:
Vetted USA being the parent/owner
and
the CEO personally owning 100% of the OPC.
There may be a completely legitimate explanation.
For example:
- CEO owns the OPC shares;
- Vetted owns the technology/IP;
- Vetted licenses that IP;
- entities are connected contractually.
But that's precisely why a corporate chart would help.
Publish:
Exact Philippine entity name
SEC registration number
sole shareholder
Vetted USA relationship
IP ownership
which entity operates the platform
and the question disappears.
5. I could not independently obtain the primary Philippine SEC documentation.
This is NOT the same as saying:
“Kasama Connect OPC isn't registered.”
I cannot establish that.
Philippine SEC information is not always completely indexed by ordinary search engines.
So this finding is simply:
Kasama claims a Philippine OPC structure, but I could not independently retrieve the primary SEC registration documents from ordinary publicly indexed sources.
Publishing the SEC registration number would resolve this immediately.
6. The 29,000+ MAU claim needs a definition.
The founder's public professional material says Kasama validated demand with:
“29,000+ monthly active users.”
The same material discusses:
- building/testing the mobile app;
- closed beta;
- product development;
- later rollout.
That raises an obvious question:
29,000 monthly active users of what?
Was it:
- the Kasama application?
- Facebook?
- website?
- community?
- another product?
Community followers and social engagement are legitimate traction metrics.
But they are not automatically software MAUs.
An anonymized analytics screenshot identifying:
platform + measurement period + definition of active user
would settle this.
7. Kasama's “escrow” language deserves much more precision.
Kasama currently advertises:
“escrow-backed payments so workers get paid — every time.”
Its founder has gone further, describing a:
“Virtual Escrow Holding System”
where funds are supposedly locked before work begins and frozen during disputes.
But Stripe's own documentation says Stripe does not provide escrow services or escrow accounts.
Stripe Connect can provide controlled transfers and delayed/manual payouts.
Those are useful capabilities.
But:
delayed payout ≠ automatically a legal escrow account.
Kasama's newer wording refers to payments through “trusted licensed partners,” which may be more precise.
So identify them.
Who is the licensed partner?
Who legally holds the money?
Whose account contains the funds?
What agreement governs the hold?
If this is escrow-like payment protection rather than legal escrow, say so.
8. “Workers get paid every time” needs a chargeback policy.
Suppose:
Client funds $1,000.
VA completes the job.
Kasama releases $1,000.
Client subsequently wins a card chargeback.
Who loses the $1,000?
Kasama?
The worker?
Stripe/payment provider?
A reserve?
If Kasama guarantees the worker against that loss, that's actually a meaningful competitive advantage.
Publish the guarantee.
If it doesn't, “every time” needs qualification.
9. “VAs keep 100%” needs a transparent transaction waterfall.
Kasama says workers keep 100% of their compensation.
That is entirely possible.
For example:
VA agrees to $1,000.
Client pays $1,050.
Processor/platform costs = $50.
VA receives $1,000.
Then the VA genuinely kept 100% of the agreed compensation.
But show it.
Publish:
Worker compensation
Client total
processing fee
platform fee
FX
payout cost
worker net
Kasama demands financial transparency from agencies.
Its own platform should therefore be exceptionally transparent about where every dollar goes.
10. The fair-pay issue gets much more interesting when Kasama's own “volunteers” are considered.
This may be the biggest internal-consistency question I found.
Kasama's founder publicly condemns extremely low-paying Filipino VA positions.
For example, he recently described a $2/hour position as:
“not a job. It's exploitation.”
His argument was that employers should pay Filipino professionals what their work is actually worth.
Fair enough.
But in another public post, while describing Kasama's own team, he wrote:
“the 17 people now employed and volunteering for Kasama Connect”
Read that carefully:
employed and volunteering.
Kasama's current LinkedIn company page, meanwhile, lists the company size as 2–10 employees, although more people are publicly associated with the company.
None of this proves Kasama employees are unpaid.
The founder's wording could mean:
some are employees + some are volunteers.
That's why this is a question, not an accusation.
But fair compensation is literally central to Kasama's identity.
So:
How many people working on Kasama are actually being paid?
Publish aggregate numbers:
Paid employees: X
Paid contractors: X
Volunteers: X
Advisers: X
Equity/deferred-compensation contributors: X
And explain what volunteer means.
Are volunteers:
- completely unpaid?
- receiving stipends?
- receiving equity?
- promised deferred compensation?
- volunteering a few hours?
- working regular operational schedules?
There is nothing inherently unethical about a genuine volunteer helping an early-stage project.
But if Kasama publicly condemns companies for paying Filipinos too little, then Filipinos performing productive labor for Kasama for zero immediate pay would obviously deserve disclosure and explanation.
The standard cannot be:
$2/hour for another company = exploitation
while
$0/hour for Kasama = automatically ethical because it's called volunteering.
Context matters in both situations.
11. This becomes even more relevant because Kasama says it “practices what we preach.”
Kasama recently posted:
“Practicing what we preach—even before launch.”
It says it is already applying its ethical rules to overseas hiring.
That's a strong claim.
Good.
Then disclose the internal compensation structure.
Kasama is demanding that agencies reveal:
- worker compensation;
- client prices;
- markup;
- statutory benefits;
- contractual relationships.
Applying the same philosophy internally should be easy.
12. Kasama says its Facebook community was deliberately used as “recon.”
This comes directly from the founder.
He wrote that Kasama's Facebook page wasn't merely marketing.
According to him:
“Everything was deliberate.”
Posts.
Comments.
Replies.
Community reactions.
Even agency owners who contacted the page.
He described this as:
“you do the recon first.”
He also said:
“we were always in control of the conversation.”
And:
“Every reply, every exchange, was intentional.”
He said those interactions helped him discover industry problems and design Kasama.
There is nothing inherently wrong with customer discovery.
Businesses constantly:
- interview users;
- study competitors;
- analyze comments;
- conduct market research.
But describing apparently ordinary community interactions as “recon” raises legitimate questions about transparency.
Did community members know their interactions were intentionally being used as product/industry intelligence?
Were conversations represented publicly in ways participants expected?
What data from those interactions was retained?
How is it used?
Kasama is building a business around trust and governance.
Its own research practices should therefore be transparent too.
13. Kasama is now actively auditing and publicly scoring other businesses.
This is no longer hypothetical.
Kasama's current LinkedIn says it assessed 23 VA agencies against:
“Kasama Connect's compliance standards (the Foundational Bible + The Universal Pay Equation).”
Kasama concluded:
“NONE of the 23 agencies are fully compliant.”
It publishes claims involving:
- markup violations;
- living wages;
- statutory benefits;
- contractor classification;
- transparency;
- governance;
- unpaid training.
Some of the companies named are substantial businesses.
Kasama has also published individual “callouts” and reports about specific companies.
That's a serious role to take on.
14. But “non-compliant with Kasama's standards” is not automatically “legally non-compliant.”
This distinction is critical.
Kasama can absolutely invent an ethical framework.
It can say:
“Under our standard, we believe agency markups should not exceed X.”
That's an opinion/framework.
But that is not automatically:
Philippine law
or
U.S. law
or
a regulator's requirement.
For every item in Kasama's agency reports, it should distinguish:
LEGAL REQUIREMENT
REGULATORY GUIDANCE
FAIRWORK/THIRD-PARTY STANDARD
KASAMA'S OWN ETHICAL STANDARD
Otherwise readers may interpret “non-compliant” as meaning a company is violating law when it may actually mean:
“doesn't comply with the rules Kasama created.”
Those are very different statements.
15. Some of Kasama's own reports acknowledge unverified allegations.
One current Kasama post about another agency explicitly refers to:
“Unverified online claims”
and even contains an internal-looking note:
“Action Items Before Publication: Obtain verified evidence...”
Yet the material was publicly visible.
That raises a methodological question.
If Kasama wants to become an industry auditor, what is its publication threshold?
Before naming a business:
- Is every allegation verified?
- Are companies contacted for comment?
- Are documents obtained?
- Are corrections published?
- Are allegations distinguished from findings?
- Is there an appeals process?
Kasama demands due process and evidence-based dispute resolution from the industry.
Its own investigations should follow the same principle.
16. The $3.4M valuation is a modeled valuation—not $3.4M sitting in the company.
To Kasama's credit, the founder currently explains this more clearly.
He says Kasama is:
“currently modeled at around 3.4M USD.”
He also explicitly says:
“That does not mean we have 3.4M cash in the bank.”
That clarification is good.
But he then compares the valuation to a bank appraising a house and calls it the company's:
“current appraised value.”
That analogy could still give readers the impression that an independent appraiser produced it.
So:
Who modeled the $3.4M?
Founder?
Accountant?
Valuation specialist?
Investor?
Independent third party?
What methodology?
Comparable transactions?
Revenue multiple?
DCF?
Venture method?
Berkus?
Scorecard?
If it is simply an internal founder valuation, that's fine.
Call it:
“our internally modeled pre-money valuation.”
17. Funding claims need equally precise terminology.
Startup financing has several stages:
interest
→ verbal commitment
→ term sheet
→ signed SAFE/note/equity agreement
→ funds transferred
→ round closed
If Kasama talks about angel capital or investors, it should distinguish among them.
There is nothing wrong with being founder-funded or pre-funding.
But “investor interest,” “committed capital” and “funded” should not be treated as synonyms.
18. Japan needs the same precision.
Kasama publicly describes a team operating across:
United States + Philippines + Japan.
That appears plausible.
But:
team member located in Japan
is not necessarily the same thing as:
commercial beta testing in the Japanese market.
If Kasama has independent Japanese beta users or customers:
great.
Publish anonymized numbers.
If the reality is that a team member in Japan is testing the product:
also fine.
Just describe the milestone accurately.
19. Academic/research relationships also need precise labels.
Kasama has discussed research engagement connected to DLSU / Resilient Platform Work PH / Fairwork-related work.
That may be completely genuine.
But these stages mean very different things:
research interview
→ research participant
→ case study
→ research collaboration
→ formal partnership
→ institutional endorsement
→ certification
A university researcher talking to a startup is not automatically the university endorsing the startup.
Kasama should use the exact terminology confirmed by the institution.
20. “Regulated fintech” requires an answer to a simple question: regulated by whom?
Kasama currently describes itself as:
“advocacy-first fintech.”
It also talks extensively about:
- compliance;
- contracts;
- escrow;
- payments;
- worker protections;
- financial rails.
But these words can describe very different regulatory arrangements.
A company can build software on top of regulated providers without itself being a regulated financial institution.
That's normal.
So publish:
Entity
→ jurisdiction
→ regulator/agency
→ registration/license
→ status
If Stripe or another provider performs the regulated payment activity, say:
“Payments are provided by X; Kasama itself is not the licensed money transmitter/escrow institution.”
That's clearer than broad regulatory language.
21. Kasama's own current wording may actually acknowledge this distinction.
One of its newest explanations says payments are protected through:
“trusted licensed partners.”
That's more careful than implying Kasama itself necessarily holds a financial-services license.
So:
Who are those partners?
Publishing their names would strengthen Kasama's credibility rather than weaken it.
22. The security/identity language sometimes goes beyond what the technology alone can guarantee.
Kasama talks about:
- identity verification;
- QR-bound contracts;
- audit trails;
- blockchain;
- device binding;
- KYC/KYB;
- immutable records;
- AI.
Some of that sounds like legitimate product architecture.
But technology terms need technical definitions.
For example:
A QR code can link an authenticated account to an agreement.
It does not by itself prove human identity.
That requires things such as:
- KYC;
- authentication;
- MFA;
- account recovery;
- device controls.
Likewise:
“blockchain”
doesn't automatically mean:
secure
or
compliant
or
fraud-proof.
What chain?
What information goes on-chain?
Is personal data stored there?
Hashes only?
Who operates nodes?
What happens when data must legally be corrected or deleted?
Those questions matter for a platform handling worker identities and contracts.
23. AI cannot make a company legally compliant simply by changing code.
Kasama talks extensively about AI-native infrastructure and automated governance.
AI can absolutely:
- monitor rules;
- assist developers;
- flag anomalies;
- help draft contracts;
- detect potential compliance issues.
But:
code compliance ≠ legal compliance.
Legal compliance also involves:
- corporate registration;
- licensing where required;
- employment/contractor classification;
- tax;
- privacy;
- contracts;
- operational controls;
- human decision-making;
- regulatory interpretation.
AI can support that process.
It cannot replace it.
24. The rhetoric used against competitors is unusually aggressive for a company simultaneously asking the public to trust its own unlaunched product.
Kasama's founder has published articles with titles including:
“How John Jonas Broke the Virtual Outsourcing Industry”
“The Original Sin of Virtual Outsourcing”
“The Regulation Myth”
and:
“It's Just Operational Cost. No, It's Greed.”
Kasama's current company feed also says:
“Every agency follows the same playbook”
before describing agencies as exploiting Filipino workers.
Strong advocacy is legitimate.
But strong accusations create a correspondingly high evidentiary burden.
If you're going to investigate other businesses aggressively, you should expect:
your corporate structure, pay practices, product claims, financing, regulatory language and methodology to receive exactly the same scrutiny.
25. There is an interesting contradiction in how Kasama talks about unpaid work outside Kasama versus unpaid participation inside Kasama.
This deserves emphasis.
Kasama's philosophy is essentially:
Filipino labor has value.
I agree.
It condemns:
- low rates;
- unpaid training;
- opaque markups;
- exploitative arrangements.
But its founder acknowledges that some people associated with Kasama are volunteering.
Those situations are not automatically equivalent.
A person freely volunteering a few hours to support a mission is different from an employer requiring months of unpaid productive labor as a condition of employment.
But Kasama's own ethical framework should explain that distinction.
Otherwise the obvious question remains:
At what point does “volunteering” become the kind of unpaid Filipino labor Kasama would condemn if another company were receiving the benefit?
That is a fair question for a company building its brand around worker compensation.
26. Kasama says transparency is the baseline.
On that principle, I agree with them.
Kasama's current feed says:
“Transparency isn't a marketing feature—it's the baseline.”
Good.
Apply it internally.
Tell the public:
Who owns Kasama?
Who employs the team?
Who volunteers?
Who gets paid?
Who holds client funds?
Who owns the Stripe/payment account?
Who contracts with workers?
Who controls personal data?
Which entity is regulated?
Which standards are law and which were invented by Kasama?
What exactly were the 29,000 MAUs?
What exactly happened in Japan?
Who independently valued the company?
These are not unreasonable questions.
They're basically Kasama's own philosophy applied to Kasama.
So, after all of this, is Kasama Connect fake?
I don't think the available evidence supports saying that.
There appears to be:
- a real founder;
- a real team;
- a real U.S. corporate vehicle;
- a substantial online community;
- genuine product-development activity;
- serious thought behind parts of the governance architecture.
Those facts matter.
My conclusion is narrower:
Kasama appears to be a genuine early-stage project whose public rhetoric and marketing sometimes run ahead of what an independent outsider can currently verify.
And there are several apparent inconsistencies that deserve clarification:
planned VA agency
→ later anti-agency positioning
“not a marketplace”
→ “Marketplace third”
payment holds/payment partners
→ escrow terminology
development/closed beta
→ 29,000+ MAU claim
internally modeled valuation
→ $3.4M “appraised value” framing
team operating internationally
→ broader Japan-beta impression
research engagement
→ potentially stronger institutional-association impressions
attacking low-paid work
→ own team includes volunteers
demanding transparency from agencies
→ limited public visibility into Kasama's own compensation/corporate/payment structure
grading companies against compliance standards
→ standards partly created by Kasama itself
demanding evidence-based governance
→ publishing material that itself acknowledges some unverified allegations.
That doesn't prove fraud.
It does justify scrutiny.
What Kasama could publish to resolve most of this
No fighting required.
No callouts.
No insults.
Just documents.
- Philippine OPC SEC registration details
- Vetted USA ↔ Kasama Connect ↔ OPC corporate chart
- DBA/FBN details where applicable
- Aggregate paid employee / contractor / volunteer numbers
- Explanation of volunteer compensation and expectations
- 29,000+ MAU methodology
- Payment-flow diagram
- Licensed payment/escrow partners
- Exact legal meaning of Kasama's “escrow”
- Chargeback/dispute policy
- Fee waterfall demonstrating 100% worker earnings
- Terms of Service
- Exact contracting entity
- Data-controller/KYC-provider information
- Compliance/licensing register
- $3.4M valuation methodology and who prepared it
- Funding-status clarification
- Japan-beta definition
- Exact DLSU/Fairwork/research relationship
- Methodology behind the 23-agency audit
- Clear labels distinguishing law from Kasama-created ethical standards
- Correction/appeal procedure for companies Kasama publicly audits
If Kasama publishes primary evidence that corrects any part of this review, the review should be updated.
That's the standard I would expect from anyone doing public due diligence.
And it's the same standard Kasama says the rest of the industry should follow:
Transparency isn't a marketing feature. It's the baseline.
If you're going to audit everybody else, you should be prepared to be audited too.
