bangkok / fintech development
build partner for series a fintech teams. queue-extension when your internal team is six months behind plan.
a bangkok series a fintech team at t-one building or one of the sathorn towers runs a stack of next.js plus postgres on the aws region of their choice, with linear and cursor and claude code already in production for one or two internal workflows. the build queue is always six months ahead of headcount. we are the build partner you hire when the board wants kyc v2, a lao expansion module and ai underwriting in parallel and the internal team can only deliver one. we pick up where your team's queue ends. priced per sprint, scoped in a 30-minute call, shipped in production not in a proof of concept.
scope a fintech sprint01 . why bangkok fintech
we build for fintech teams funded by the active thai investor ecosystem. 500 global tuktuks, beacon vc (kasikornbank), east ventures, scb 10x (siam commercial bank's venture arm) and krungsri finnovate (bay) are the names a series a board recognises. these are the ecosystem context, not our clients. add accel, openspace and sequoia india southeast asia and the bangkok series a fintech tier has real depth of capital. the operating layer is a hundred or so technical co-founders running teams of 20 to 80 engineers across phrom phong, asoke and sathorn.
the stack pattern is shared across the tier. next.js on the front-end. postgres plus prisma for the data layer. aws region selectable per the team's bot residency posture. linear plus cursor plus claude code for the engineering process. promptpay, 2c2p or omise on the checkout side. a payment partner integration with bay, scb, kbank or kbtg via krungsri finnovate. internal tooling is whatever the cto built when the team was five people, now stretched to forty. the build queue is the constant: kyc v2 to onboard thai sme clients, a lao or vietnam expansion module, the ai underwriting feature the cto promised in the deck, plus the bot regulatory reporting layer that landed in the latest notification.
we are the build partner you hire when the queue is six months ahead of plan. not the team that replaces the internal engineers. the team that picks up the parallel workstream the cto cannot ship while running the core product. priced per twelve-week sprint, scoped in a thirty-minute call, shipped in production not in a powerpoint. typical sprint shapes: a kyc v2 onboarding flow including thai national id verification, a lao or vietnam expansion module with local payment rail wiring, an ai underwriting feature on claude api with the human-in-the-loop checkpoint that bot examiners expect to see, or a bot regulatory reporting pipeline that pulls data from production postgres into the supervisory format on a daily or weekly schedule.
the credibility check is the work itself. brussels-founded, bangkok studio since 2024, six-year-old practice. board of innovation, the antwerp innovation consultancy, sits in the longest-retainer slot. horsetonic as the recent next.js plus stripe rebuild reference. enky as the b2b platform reference. real production work for real clients, not a slide deck of logos. trusted enough to drop into the cto's slack as the senior engineer the team would have hired in q1, except the headcount line is already maxed out.
02 . what we build for bangkok fintech
01
kyc v2 onboarding flow. thai national id verification, dopa integration, kyc form, document capture, aml screening, bot-compliant audit trail. shipped to production in a twelve-week sprint. see custom apps→
02
regional expansion module. lao or vietnam expansion with local payment rail wiring (bcel, vnpay, momo), local kyc requirements, locale switching, regulatory reporting per jurisdiction. multi-country support built once, reused across the expansion roadmap. see custom apps→
03
ai underwriting feature. claude api on a credit scoring or wealth-product recommendation workflow. retrieval over the team's historical loan or transaction data. bot-compliant human-in-the-loop checkpoint. explainability output in the format a credit officer or examiner expects. see ai integration→
04
bot regulatory reporting. supervisory reporting pipeline pulling from production postgres into the bot template. daily or weekly cadence, audit log, data lineage from source to filing. handles the section 8 lending business act reports and the bot notification 11/2562 templates. see erp integration→
05
internal dashboard or admin panel. the dashboard the cto would have built in q1 if the team was not shipping the core product. next.js plus tailwind, role-based access, audit log, integrates with the existing claude code stack. ships in four to six weeks per dashboard. see custom apps→
03 . case anchor
04 . the sprint method
week 1-2
weeks 1 to 2
thirty-minute kickoff plus a paid two-week architecture sprint. spec document, data model, api contracts, security model, bot or pdpa compliance considerations, integration map. you sign off before any production code is written.
week 3-8
weeks 3 to 8
weekly demo to the cto. production deployment on your aws or vercel. linear board synced. you own the code from the first commit. one engagement lead, direct slack or line channel during bangkok business hours.
week 9-10
weeks 9 to 10
qa, load test, security review. fix list closed inside the sprint. dns cutover or release coordination with your internal team. lighthouse 95+ for any consumer-facing surface, security review for any sensitive data flow.
week 11-12
weeks 11 to 12
production monitoring, post-launch bugfix window, handover document, knowledge transfer to your internal team. ninety-day care window included for the sprint deliverable. no second contract required.
05 . questions from bangkok ctos
01
do you work alongside our internal engineering team?
yes. we pick up the parallel workstream the cto cannot ship while running the core product. one engagement lead from our side, direct slack or line access to your senior engineers, weekly demo synced to your sprint cadence. we are not a body shop sending six juniors. one senior who owns the sprint outcome.
02
do you understand bot compliance and the lending business act?
we build bot-aware. supervisory reporting templates, section 8 lending business act audit trails, bot notification 11/2562 customer protection rules, mas equivalents for the lao or vietnam expansion. we co-author the regulatory approach with your compliance lead or external counsel in week 1 to 2 of the sprint, not after the build ships.
03
what stack do you build on?
next.js plus typescript plus postgres plus prisma is the default. vercel + supabase, aws region selectable. supabase or self-hosted postgres for the data layer. claude api for ai workflows, claude code as the engineering interface. payment rail integration with promptpay, 2c2p, omise, scb pay, kbank pay or bay api depending on your current setup. no framework choice you cannot replace.
04
how do you handle data residency for thai customer data?
aws region selectable per the team's bot residency posture. for stricter residency requirements (some bot-regulated entities, some boi-promoted workloads) we deploy in-country on a thai cloud provider or an in-region aws deployment. data flow mapping is locked in week 1 to 2 of the sprint. cross-border data transfer to claude api is documented under pdpa b.e. 2562, sections 19, 23 to 29, 37 (cross-border per section 28), with the legitimate basis and the safeguards in place.
05
what does a sprint cost?
twelve-week sprint priced per scope. priced per sprint deliverable, not per hour. the architecture sprint in weeks 1 to 2 is a separate paid step and refundable if the architecture does not unlock a go-build decision. concrete numbers land in your inbox after a thirty-minute call once the sprint shape is locked.
06
do you have other thai fintech clients we can reference?
bangkok studio since 2024. we shipped the enky b2b platform rebuild in late 2024 and the horsetonic next.js plus stripe ecommerce launch in early 2025, and brought six years of brussels-tier engineering practice into every build. our governance discipline carries from board of innovation at fortune-tier scale. for a thai fintech series a, the right evaluation is a thirty-minute call plus a two-week paid architecture sprint, not a logo wall.
07
what about ip ownership?
you own the code from the first commit. the github repo is yours. the deployment is on your aws or vercel account. the engagement contract documents ip assignment explicitly. no escrow, no licence-back, no third-party dependency you cannot replace. the only thing we keep is the operating playbook for our own internal use across future sprints.
06 . go further
ready for week 1?
book a thirty-minute call. we reply inside 24 hours with a sprint shape or an honest no. brussels-registered, bangkok-based, no body shop, no proof of concept theatre.