Who we build for How we work Kanji Case studies Markets FAQ Talk to us
Custom software · Six markets · Engineers and AI

Build the application your competitors are already planning.

Thiran Global pairs senior engineers with AI build systems to design, ship and run custom applications for small and mid-sized businesses. Weeks to first release, not quarters. You own every line.

Book a scoping call See what we've built
Every change reviewed by an engineer Fixed price for the first release Code, data and accounts in your name
Why now

The cost of building software just fell. Someone in your market has noticed.

For twenty years custom software was something only large companies could afford. That is over. A small team of engineers working with AI build systems now ships in weeks what used to take a year. The businesses that move first get software shaped around how they actually operate. Everyone else keeps paying for generic tools, and for the staff hours spent working around them.

Lower cost to serve

An operator whose quoting, dispatch, invoicing and customer updates run on their own system needs fewer people per order. That saving goes to margin, or to price. Either way it is a weapon.

Faster to answer

Quotes in minutes rather than days. Orders confirmed before the customer opens a competitor's site. Calls answered during the meeting, not after it. Speed is a feature customers can feel.

Harder to copy

Off-the-shelf tools are available to everyone, including the firm across town. Software built around your routes, your stock, your clients and your pricing is not.

The question is no longer whether a business your size can afford custom software. It is whether you can afford to be the last one in your market without it.
Find out what we'd build for you
Who we build for

Businesses with real operations and a margin to protect.

We work with owner-led and founder-led companies from roughly ten to a few hundred people. Big enough that process matters. Small enough that the owner still feels every inefficiency.

Consulting and professional services

Proposals drafted from your past work, engagement tracking, time and billing that matches how you actually sell, and client portals that make a ten-person firm feel like a hundred.

We build: proposal engines · client portals · intake and scheduling · billing

Logistics and delivery

Dispatch and routing built around your fleet, live tracking your customers trust, proof of delivery, driver apps, and connections to the courier networks you already use.

We build: dispatch engines · driver apps · tracking · courier integrations

Ecommerce operators

Inventory that reconciles itself across channels, returns handled without a ticket queue, customer service that answers at two in the morning, and buying decisions informed by what actually sold.

We build: stock sync · returns flows · multilingual service agents · ops dashboards

Field services and trades

Job scheduling, quoting on site, parts and stock, and invoicing the same day. Technicians stop doing admin at the kitchen table and the office stops chasing paperwork.

We build: scheduling · on-site quoting · job apps · same-day invoicing

Hospitality and multi-site restaurants

Ordering, kitchen and delivery flows under one roof, menus that stay in sync across every channel, and third-party courier integration that turns a fixed driver cost into a per-order one.

We build: order hubs · menu sync · kitchen displays · Uber Direct and courier links

Healthcare and clinics

Intake, scheduling and reminders that cut no-shows, patient communication that does not depend on the front desk, with the privacy requirements of your market handled from day one.

We build: intake · scheduling and reminders · patient portals · referral tracking

Wholesale and distribution

Trade ordering portals, price lists per customer, stock visibility for reps on the road, and the accounting and ERP connection nobody wanted to write.

We build: B2B order portals · rep apps · pricing engines · ERP connectors

Property and facilities

Maintenance requests, contractor dispatch, inspections and tenant communication in one place, so a small team can run a large portfolio without the inbox running them.

We build: request portals · contractor dispatch · inspection apps · owner reporting
How we work

Engineers decide. AI does the heavy lifting. A person reads every line before it ships.

We are not an agency that bought a subscription to a coding tool. We run our own AI build systems: pipelines that draft, test and triage under the direction of engineers who have shipped production software for years. The split is deliberate.

What our engineers do People

  • Scope the problem with you and say no to software that will not pay back.
  • Design the system, the data model and every integration.
  • Make every architecture, security and privacy decision.
  • Review and approve every change before it reaches your customers.
  • Run the launch, and stay on afterwards.

What our AI systems do Kanji

  • Write first drafts of code, tests and documentation from the engineer's design.
  • Reproduce, triage and fix routine bugs, then submit the fix for review.
  • Run end-to-end tests against your real customer journeys before every release.
  • Draft specs, release notes and handover documents from the actual work.
  • Watch production and flag what looks unusual before anyone calls.
The result

A senior team's judgement at a build pace no traditional agency can match. You get the speed of AI with the accountability of people who put their name on the work, and a bill that reflects the hours the machines took, not the hours a person would have.

Our own system

The reason a small team can promise what we promise.

Every Thiran build runs on Kanji, an autonomous engineering system we built for ourselves and do not sell. It works the way a chief technology officer would if one never left the building: it plans the work, writes and tests the first draft, reviews its own changes, runs your real customer journeys before every release, and watches production afterwards. Our engineers direct it and sign off on every line.

  • Plansturns a brief into a build plan and a price
  • Buildsfirst drafts of code, tests and docs
  • Reviewsreads every change before a person does
  • Provesyour real journeys, before every release
  • Watchesproduction, around the clock
  • Learnsevery fix becomes a lasting check

You will never log into it. You only see what it produces: senior-team quality at a small-team price, release after release.

Not a product. Our advantage.

Built to still be working the year after launch.

You own everything

Repositories, cloud accounts, domains, data. In your name from the first week. If we part ways, you keep it all and any competent team can pick it up.

Tested against the real thing

Automated tests cover your actual journeys end to end: an order placed, a job quoted, a call booked. They run before every release, not when someone remembers.

Connected to what you already use

Xero, QuickBooks, Sage, Shopify, WooCommerce, HubSpot, Stripe, Uber Direct, your ERP. Your team keeps the tools that work and stops double-keying into the ones that do not.

Not locked to one AI vendor

The models behind your product are swappable. When a provider raises prices or a better one appears, we move you across. You never pay to rebuild from scratch.

Compliance by market

GDPR and UK GDPR, POPIA in South Africa, the Australian Privacy Act, US state privacy law. Designed in at the data-model stage, not bolted on before launch.

Run and watched

Monitoring, alerting and support hours that overlap your working day, whichever of our six markets you are in. We find out before your customers do.

The process

From a problem to a running product in five steps.

No discovery phase that costs more than the software. No demo built to win the deal and thrown away afterwards. The plan is written down, priced, and then built exactly as agreed.

01
One hour · free

Scoping call

We learn how your business runs, where the margin leaks, and whether software is actually the fix. If it is not, we say so and you lose an hour.

02
One to two weeks · fixed fee

Blueprint

A written plan: the screens, the data, the integrations, what ships first and what waits. It ends with a fixed price and date for the first release, before you commit to building.

03
Two-week sprints · weekly demos

Build

Working software every Friday, in your hours. You test it with real orders, real clients and real stock while it is still cheap to change your mind.

04
Before anyone sees it

Prove

Automated tests cover the journeys your customers actually take. A pilot with a slice of them runs before the whole business depends on it.

05
Monthly · cancel any time

Run and grow

We watch production, fix what breaks, and ship the next most valuable thing. Month by month, under a plan you can stop whenever the numbers say so.

Case studies

What it looks like when a small business stops waiting for software.

Client names are withheld at their request. Each of these is a business that was being squeezed by a larger, better-tooled competitor, and decided to stop being the one with the worse tools.

Logistics and deliveryHospitalityMobile apps

A regional food-delivery marketplace takes on the national platforms.

United States · 40+ partner restaurants · own driver fleet
9 weeksfrom scoping call to first live orders
Weeklyrelease cadence, up from monthly
0 hrsweekly manual payout reconciliation, down from a full day
2 engineersrun the whole platform with AI build support

The situation

A marketplace serving independent restaurants was competing with national platforms that charge restaurants close to a third of every order. Its own stack was a patchwork of separate ordering, dispatch and payment tools, reconciled by hand every week. Growth meant more spreadsheets, not more margin.

What we built

Customer and restaurant apps, a driver app with live tracking, a dispatch engine that assigns and re-assigns orders by distance and kitchen time, card payments with automated restaurant payouts, and one operations console the owner can run the business from.

Where AI changed the build

Every night an automated suite exercises the entire order journey: placed, accepted, cooked, dispatched, delivered, paid out. Routine bugs found by it are reproduced and fixed by our AI systems and handed to an engineer for review. That is what let a two-person team move from monthly to weekly releases without the quality slipping.

HospitalityCourier integrationOperations

A quick-service restaurant group turns a fixed driver cost into a per-order one.

Australia · multi-site group · Uber Direct
3 → 1delivery tablets on the counter replaced by one screen
18courier edge cases tested before the first live order
Per orderdriver cost, previously fixed whether orders came in or not
1 releaseto go live across every site

The situation

Delivery orders arrived through three apps on three tablets and were re-keyed into the till. Sold-out items kept selling on the channels nobody had updated. Drivers were paid for the shift whether or not the orders came, so quiet nights lost money twice.

What we built

One order hub across every channel, menu sync so a sold-out item disappears everywhere at once, and an Uber Direct integration that requests a courier per order with a live quote, with the in-house drivers kept as a fallback for peak hours.

Where AI changed the build

Courier APIs are mostly edge cases: cancellations, failed pickups, address corrections, partial refunds. Our AI systems generated and ran test suites for every one of them before a real customer was involved, and drafted the integration documentation from the real traffic. The engineer's time went on the decisions, not the plumbing.

ConsultingAI phone agentCRM

A fourteen-person advisory firm stops losing clients to voicemail.

United Kingdom · professional services · UK GDPR
100%of calls answered, including during client meetings
Same hourfrom enquiry to booked consultation, previously next day
400+generated caller scenarios tested before go-live
Own accountscall data and transcripts held in the firm's name

The situation

Partners were in meetings when prospects called. Enquiries went to voicemail, were returned the next day, and a good share had already gone to a firm that picked up. The team knew the number was bad and had stopped counting it.

What we built

A phone agent that answers in the firm's voice, qualifies the enquiry, books a consultation into the right partner's calendar and writes a summary into the CRM, with a hand-off to a person for anything sensitive. Built under UK GDPR, with every recording and transcript in the firm's own accounts.

Where AI changed the build

The agent's conversations were tested against hundreds of generated caller scenarios, from the straightforward to the awkward, before a real caller ever heard it. In production, transcript review flags the conversations a partner should listen to, so the firm reviews minutes a week rather than hours.

EcommerceCustomer serviceMultilingual

A specialist online retailer answers in four languages without hiring in any of them.

Netherlands · selling into NL, BE and DE · Shopify and warehouse system
Majorityof tickets resolved without a person involved
Secondsfirst response time, previously hours
4 languagesDutch, German, French and English from one system
Retentionwhere the service team now spends its time

The situation

Customer service ran through a shared inbox. Returns, "where is my order" and sizing questions made up most of the volume, in three languages, and every one of them needed a person to look something up before replying.

What we built

A service layer that answers order status, starts returns and handles sizing questions in Dutch, German, French and English, connected to the shop platform, the warehouse system and the carrier. Everything else lands in one queue for a person, with the context already gathered.

Where AI changed the build

Answers draw on the live order, stock and shipment data rather than a script, so the system says what is true for that customer today. Every category of reply was tested against the retailer's own past tickets before launch, and the ones it could not handle well were routed to people from day one.

Markets

Six markets. Local rules, local hours, one team.

Our engineers are spread so that every market has overlap during its working day. Demos, support and the awkward conversations all happen in your hours, in your regulatory context.

United StatesEST–PST

Built for a state-by-state market

  • State privacy law including CCPA and its successors
  • Stripe, QuickBooks, ShipStation, major carriers
  • Support hours from Eastern through Pacific
United KingdomGMT/BST

Same-day working hours

  • UK GDPR and ICO expectations
  • Xero, Sage, Open Banking payments
  • Phone agents with UK numbers and accents
AustraliaAEST

Delivery and courier heavy

  • Privacy Act and the APPs
  • Xero, MYOB, Australia Post, Uber Direct and courier networks
  • Engineers in your morning, not your night
SpainCET

Spanish-first products

  • GDPR and Spain's electronic invoicing rules
  • Bizum, Redsys, local logistics providers
  • Spanish and English as standard, Catalan on request
South AfricaSAST

Designed for unreliable power and data

  • POPIA compliance from the data model up
  • PayFast, Yoco, Ozow and local couriers
  • Offline-first apps that survive load-shedding
NetherlandsCET

Built for the Benelux and Germany

  • GDPR with Dutch Authority for Personal Data guidance
  • iDEAL, Mollie, Exact, Twinfield, PostNL
  • Dutch, English and German products
Where to start

Nobody wakes up wanting "custom software". They wake up to one of these.

Find the sentence that sounds like your Monday morning. That is the conversation to have first. We will tell you what to build, and sometimes that it is not software at all.

"We quote by hand and lose the job while we're doing it."Field services · consulting · wholesale "Our drivers run on a group chat and a spreadsheet."Logistics · delivery · hospitality "Three sales channels, three stock counts, none of them right."Ecommerce · wholesale · retail "Our best people spend half their day on admin."Consulting · clinics · property "We paid an agency last year and never got to launch."Any sector · rescue and finish "A competitor just dropped their prices and we can't see how."Any sector · margin analysis first
Questions

The things people ask on the first call.

Straight answers. If yours is not here, ask it in the form below and a person will reply.

Does AI write your code?

Our own system, Kanji, produces first drafts of code, tests and documentation, and handles routine fixes. Engineers design the system, make every decision that matters, and review every change before it ships. Nothing reaches your customers without a person having read it.

Who owns the code and the data?

You do. Repositories, cloud accounts, domains and data are in your name from the start. If we part ways, you keep everything and any competent team can continue the work. There is no platform of ours you depend on.

What does it cost?

The blueprint gives you a fixed price for the first release before you commit to building. Because AI carries the routine work, that price is typically a fraction of a traditional agency quote for the same scope, and the timeline is shorter. Ongoing work runs on a monthly plan you can stop.

How do you work across six time zones?

Our engineers are distributed so that each market has overlap during its own working day. Weekly demos and support happen in your hours. The AI systems run around the clock, so a bug reported at your close of business is often fixed and awaiting review by your morning.

We already have a half-built system. Can you finish it?

Send it over. We review it and tell you whether to finish it, fix it or start again, with reasons and a cost for each. Roughly half the systems we see are worth finishing.

How do you handle privacy and compliance?

Each market's regime is designed in from the data model up: GDPR and UK GDPR, POPIA, the Australian Privacy Act and US state law. Data stays in your accounts and in the region you choose. AI providers are used under terms that exclude training on your data.

What technology do you use?

Mainstream, well-supported stacks: TypeScript and Python services, React for web, native and cross-platform mobile, Postgres, the major cloud providers. Chosen so that any engineer you hire later can read it.

Talk to us

Tell us what is slowing you down.

An idea, a stalled build, a competitor who is suddenly cheaper. The first call is a working session with an engineer, not a pitch from a salesperson. One hour, no charge, and an honest answer about whether software is the fix.

Or email [email protected]. A person replies within one working day in your time zone.