← Engineering portfolioCo-founder / Venture pilot

Afremit

A clearer way for people abroad to support a specific school fee and follow what happens next.

Illustrated Afremit test payment journey from school request to independent review
Role
Co-founder and product engineering
Priority
Private education institutions and families abroad
Stage
Working pilot with simulated payments
Also exploring
Healthcare and construction providers

Supporting a service should come with clarity

Imagine a parent in London paying a school fee for a student in Ghana. The family needs to know which institution asked for the fee, the amount and reference, and whether the school received the information it needs. The school needs an easy way to issue the request and check it against its own records. Afremit is testing that shared journey, beginning with education.

One request, a visible outcome

  • A school, clinic or construction provider applies for pilot access and an Afremit reviewer decides whether to approve testing.
  • An approved provider starts with one fee, estimate or milestone and a private reference. There is no need to upload a complete service catalogue.
  • A payer abroad opens a private code, reviews the request and accepts a stated condition for simulated release.
  • The provider submits an evidence note. An Afremit reviewer checks it before releasing test value; mismatches and disputes stay visible, with a reason recorded for decisions.

The local demo uses fictional accounts and a double-entry test ledger. A connected pilot is prepared for separate Cloudflare Pages and Supabase deployment with authenticated accounts.

A term fee from abroad

A finance officer creates a request for an autumn term fee with a student reference and a condition for confirming the allocation. A family member reviews the request and creates a simulated payment. The school supplies an allocation reference; an Afremit reviewer verifies the stated condition before the test ledger records release. If the amount differs or the payer disputes the request, the workflow stops for review.

From venture direction to testable software

As Afremit's co-founder, I helped shape the product direction and built this pilot to test the most important handoffs. The repository contains a responsive public site, role-based workspace, JavaScript service logic, Cloudflare Pages Functions, Supabase schema and migration, audit trail, and automated workflow tests. The static GitHub Pages preview explains the journey; the connected workspace needs a separate server and database deployment.

What is still being validated

The ledger simulates held, released and refunded value. Afremit does not currently take or hold money, provide escrow or insurance, quote exchange rates, or have an active payment partner. Pilot approval is access to test software, not financial verification. No active institution or investment commitment is claimed here. Any real-money service would depend on suitable partners, agreements and regulatory review.

The next evidence to gather is whether providers can onboard quickly, whether payers understand the request and release condition, and how teams handle mismatches in their everyday process. Healthcare and construction can be tested with one safe example request each.

Bring one workflow to the table

Private schools and other education providers, clinics, construction firms and potential infrastructure partners can discuss a guided test. Start with fictional or minimal information and a single request; there is no live payment required to evaluate the experience. For partnership and pilot enquiries, contact Afremit through its business page.

Engineering behind the pilot

JavaScriptNode.jsCloudflare Pages FunctionsSupabasePostgreSQLAuth and audit

See how the Afremit pilot handles a real-world question.

The source and documentation are public. The static preview is a product overview; the connected pilot is being prepared separately.

← Engineering portfolioExplore Business Systems Lab →