Topic

After launch

Running your site day to day: what to watch, what the basic numbers mean, and when to plan the next phase.

Series on this topic

Case series

Composite case

A Bangkok mid-to-high-end restaurant's journey from menu to membership: build in steps, and let every step stand up to market verification

A phase-by-phase case study built from real implementation experience: a Bangkok mid-to-high-end restaurant where orders are written by hand, the kitchen runs on call-outs and clipped paper, customers live in staff memory, and the paper menu ages, gets dirty, and needs reprints or hand-scratch-outs on price changes. It faces a complete need — ordering, kitchen, and customer systems are all missing — yet the systems on the market are either too complex, too expensive once subscriptions add up over years, or sold without any design for digitalization and marketing. With digitalization as the end goal, it builds in steps: menu digitalization first, then marketing to draw guests in, then website ordering to the kitchen (without scheduling for the chef), then a customer base profile, and finally membership and stored-value cards plus long-term social-media operations — every step standing up to market verification and scrutiny.

7 articles · 71 min total

Case series

Composite case

A boutique aesthetic clinic's digital journey: building trust before building systems

A phase-by-phase case study built from real implementation experience: a Bangkok boutique aesthetic clinic needs online booking, consultation conversion and case showcasing — and starts by making itself trustworthy online, so strangers are willing to leave a booking request at all.

6 articles · 53 min total

Case series

Composite case

A Chonburi home-repair company's journey to its repeat-customer lifeline: build the quote entry first, then lock in returning customers with a PWA

A phase-by-phase case study built from real implementation experience: a home-repair company serving a concentrated area in Chonburi, with seven technicians split into teams by specialty — plumbing, air conditioning, appliances, and leaks — where technicians work on site, quotes depend on on-site judgment, and business depends on the same neighborhood coming back. It starts with a service-scope and quote-request entry point, converges vague customer problems into trackable quote records, judges from real data how much repeat business it has and how customers return, then uses a low-cost PWA to build a repeat-customer re-discovery entry and a post-service feedback loop — forming a service, feedback, improve, re-discovery cycle, all while avoiding large dispatch systems and a native app.

6 articles · 62 min total

Series

A practical method for small-business digitalization

Seven principles for treating a website as the digital entrance, building wider systems in stages and using real operations to decide what comes next.

7 articles · 53 min total

Case series

Composite case

A print shop's digital journey

A phase-by-phase case study built from real implementation experience: a print shop that needs full digitalization from day one — and why it still builds step by step, starting from a website, letting each phase's evidence and staff experience shape the next.

6 articles · 45 min total

Case series

Composite case

A small Bangkok accounting firm goes digital: from website to PWA to AI, built in stages

A staged case drawn from real implementation experience in accounting services: a small Bangkok accounting firm whose clients submit last month's vouchers by mail, drop-off or LINE, whose intake status lives in Excel and memory, and whose bookkeeping and filings are done by hand. It faces the full need of "missing intake, tracking, tiers and extraction", but off-the-shelf cloud accounting systems either lock in their own accounting logic, cost too much per-seat, or just sell software without designing a client document-collection workflow. With digital as the end goal, it builds in stages: starting with the website and voucher uploads, then an internal intake list, then service tiers defined from real data, then a PWA client portal (tiers, profile, on-demand upgrades), and finally AI woven into daily extraction and sorting with bookkeeper review — every step must hold up to market testing.

7 articles · 72 min total

Case series

Composite case

A spa chain's digital journey: putting receipt QR feedback first

A phase-by-phase case study built from real implementation experience: a multi-branch spa chain needs cross-store consistency, and starts by turning the checkout receipt's QR code into a per-staff feedback capture — then lets that real data and the staff experience shape the next phase.

6 articles · 56 min total

Case series

Composite case

A training center's AI-assisted learning journey: build the entry point first, then talk AI

A phase-by-phase case study built from real implementation experience: a small Thai training center needs to cut repeat enquiries, see its real enrollment numbers, and ease the burden of teachers writing tests and answering questions. It starts with a unified course-info and enrollment entry point, converges enquiries into trackable enrollment data, builds a learner portal that students actually log into, and only then decides — on real usage evidence — whether to plug in AI-assisted test generation and Q&A over an API, so the center can serve more students with limited staff.

6 articles · 60 min total

Case series

Composite case

An upcountry Thai hotel's journey to reduce OTA reliance: build the entry point first, then self-booking

A phase-by-phase case study built from real implementation experience: a small upcountry Thai hotel, whose guests are mostly tourists passing through the province, starts out relying on Agoda bookings and phone/LINE contact, with high commission to carry. It builds a direct channel of its own — website room showcases, a Google Maps listing, and guided phone/LINE bookings — then judges from real enquiry and booking data whether a second phase is worth it, and finally brings repeat guests back at checkout and builds minimal self-booking. All along it avoids large hotel systems and only builds the smallest loop that reduces OTA reliance.

6 articles · 61 min total

Series

Why your business needs its own website

How a website works with Facebook and LINE as an owned information source, a functional entry point and a measurable conversion path — without pretending it is the whole business system.

7 articles · 47 min total

Articles

Case studyComposite case11 min read

A small Bangkok accounting firm goes digital, Part 6: AI joins the workflow — OCR extraction, accountant review

Once submissions and the intake list are stable, bring AI into the daily workflow: extract data from voucher images with OCR, let AI arrange it into structured drafts, and have bookkeepers review before posting. AI saves typing and sorting hours; it does not replace judgment — account assignment, posting and review stay with the bookkeeper, and final responsibility stays with the licensed CPA.

Read article
Case studyComposite case10 min read

A small Bangkok accounting firm goes digital, Part 7: retrospective — every step must hold up to market testing

From the website and voucher uploads, to the internal intake list, data-driven tiers, the PWA client portal, and finally AI extraction with review — every stop on this road answers three questions: what problem does it solve, how do we prove it, and is it worth it. Digital is the end goal, built in stages — every step must hold up to market testing.

Read article
Case studyComposite case10 min read

A home-repair company goes digital, part 3: use phase-one data to judge whether a repeat-customer entry is worth it

After the quote record has run a while, the company finally sees its business composition: which jobs make money, how high the wasted-visit rate is, what share is repeat customers. This chapter lets real numbers decide whether to invest in a repeat-customer entry — not a gut feeling.

Read article
Case studyComposite case11 min read

A home-repair company goes digital, part 4: phase two — a PWA as the repeat-customer entry, not a native app

Repeat customers are the lifeline, but to make them find you next time you don't need an app. This chapter explains why a PWA is enough: no app-store listing, no review, no dual-platform upkeep — yet it fully covers 'the customer finds the company again, fast.'

Read article
Case studyComposite case11 min read

A home-repair company goes digital, part 5: make feedback the lifeline — the service, feedback, improve, re-discovery loop

After service, invite the customer to give feedback; tie feedback to the specific technician; use it to improve service; and the satisfied customer finds the company again through the PWA. This chapter explains how the loop lands, and how technicians view 'feedback will be tied to me.'

Read article
Case studyComposite case10 min read

A home-repair company goes digital, part 6: looking back — the lifeline of a regional business is repeat customers, not a new system

Putting both phases together: build a quote entry so vague problems become data, then lock in repeat-customer return with a PWA, forming a service, feedback, improve, re-discovery loop. No dispatch system was built, no app was made — just a chain of small steps decided by real data.

Read article
Case studyComposite case10 min read

An upcountry hotel goes digital, part 3: let the front desk catch phone/LINE bookings and leave a trace

The map and website pull traffic in, but the front desk still records on paper and memory. This chapter turns direct enquiries into one record — source, room type, dates, outcome — without extra burden, so the hotel sees its direct channel's real data for the first time.

Read article
Case studyComposite case10 min read

An upcountry hotel goes digital, part 4: use phase-one data to judge whether a second phase is worth it

After the record has run a while, the hotel finally sees its direct channel: what share phone/LINE booked, which room is hottest, whether sources are growing. This chapter lets real numbers decide whether to build self-booking — not a gut feeling.

Read article
Case studyComposite case11 min read

An upcountry hotel goes digital, part 5: phase two — minimal self-booking, plus the checkout return card

Backed by phase-one data, the hotel launches minimal self-booking: only the hot room types, only availability and a deposit, complex rooms staying on human confirmation. And at checkout it hands guests a card that turns OTA guests into repeat guests booking directly next time.

Read article
Case studyComposite case10 min read

An upcountry hotel goes digital, part 6: looking back — reducing OTA reliance was a chain of small decisions

Putting both phases together: build an entry point so the direct channel can run, let data decide whether to automate, then use a checkout card to bring guests back. No large hotel system was built — just a chain of small steps decided by real data.

Read article
Case studyComposite case10 min read

A Bangkok mid-to-high-end restaurant goes digital, part 3: start with marketing — make guests able to find it, understand it, and want to come

The menu is online, but no guests are coming yet. This chapter does marketing first: fixing Google Maps and other platform info, introducing new food and interior photos, and building a website so potential customers can find the restaurant, understand it, and decide it's worth the visit. Draw the flow in first; ordering comes after.

Read article
Case studyComposite case10 min read

A Bangkok mid-to-high-end restaurant goes digital, part 4: start from the basics — website ordering to the kitchen, without scheduling for the chef

Marketing brings guests in and the menu is online; the next step makes orders lighter: website ordering, with the order automatically sent to a kitchen display. But this step deliberately has no automatic scheduling — how the work is planned stays the chef's call, so the existing workflow isn't broken. The goal is fewer missed orders, fewer chases, fewer mistakes — not a system deciding for the chef.

Read article
Case studyComposite case10 min read

A Bangkok mid-to-high-end restaurant goes digital, part 5: build a customer base profile — make a guest who came once feel like a regular

Orders hold steady; the next step keeps the guest in memory: record tastes, preferences, and birthdays — with consent and in line with privacy rules. A guest who came only once, on their second visit, gets recognized by the server and treated like a regular. It's the lowest-cost starting point for better experience and return visits.

Read article
Case studyComposite case11 min read

A Bangkok mid-to-high-end restaurant goes digital, part 6: the marketing upgrade — membership and stored-value cards, plus long-term social-media operations

The customer profile holds steady; the next step turns return visits and acquisition on: membership and stored-value cards keep regulars and build stored balance, and long-term social-media operations bring new guests in. The membership plan is decided by data, stored value carries funds and compliance boundaries, and social-media operations are a sustained investment rather than a one-off campaign.

Read article
Case studyComposite case10 min read

A Bangkok mid-to-high-end restaurant goes digital, part 7: looking back — every step had to stand up to market verification and scrutiny

From menu digitalization to membership stored value, this road wasn't walked on guesswork. Every step first answered: what problem does it solve, how do we verify it, and is it worth it. Digitalization is the end goal, but it's built in steps; and every step has to stand up to market verification and scrutiny.

Read article
Case studyComposite case10 min read

A training center goes digital, part 3: converging scattered chat enquiries into trackable enrollment data

The center turns repetitive enquiries into course pages plus an enrollment form, so every enquiry becomes a structured enrollment record. Admin is freed from repeat answers, and the school sees its enquiry volume and enrollment conversion for the first time.

Read article
Case studyComposite case10 min read

A training center goes digital, part 4: admin learns to follow up with data, and students get a first portal to log into

Admin moves from 'reading forms' to 'following up enrollments with data,' and the learner portal phase one does only four things — login, schedule, homework, grades — so students first form the habit of logging in, before any more features.

Read article
Case studyComposite case11 min read

A training center goes digital, part 5: once the portal is stable, AI plugs in over an API — test generation and online Q&A

After the learner portal has been used steadily for a few terms, the center plugs in AI over an API: it drafts test questions and answers common questions online, with teachers reviewing everything before it reaches students. AI assists; it does not replace.

Read article
Case studyComposite case10 min read

A training center goes digital, part 6: looking back — the order of entry point, data, portal and AI was not decided on a whim

A retrospective on the whole series: the most transferable lesson for training centers is a replicable order — build the entry point so strangers understand, converge data to see the truth, get the portal genuinely used, and only then plug AI in over an API and judge it by real evidence.

Read article
Case studyComposite case9 min read

A boutique aesthetic clinic goes digital, part 4: turning the request list into a follow-up habit

The request list was accurate — but a record does not convert anyone by itself. This phase gives the receptionist a simple follow-up rhythm, and lets the conversion data start telling the clinic which channels and treatments actually bring people in.

Read article
Case studyComposite case9 min read

A boutique aesthetic clinic goes digital, part 6: what this series teaches any high-trust business

A retrospective on the whole series: for a high-trust, high-ticket business, the transferable method is building trust before converting, capturing the consultation before the booking, and letting the data pick the next build.

Read article
Case studyComposite case8 min read

A print shop goes digital, part 4: turning production experience into a workflow

The admin tool's first status list came from software logic and didn't survive contact with the shop floor. The rebuilt version came from production experience — and split into two lists: one for the shop, one for customers.

Read article
Case studyComposite case7 min read

A print shop goes digital, part 6: the retrospective — letting each phase's data decide the next

The series ends where it began: with decisions. A look back at how evidence from each phase drove the next one, what the alternative 'complete system upfront' path would have cost, and honest notes on what the shop misjudged.

Read article
Case studyComposite case9 min read

A spa chain goes digital, part 4: helping staff absorb and act on centralized feedback

Feedback is now centralized, but the outcome depends on store managers and receptionists adopting it — who replies, who closes a low score, and how counter staff gently invite scans without extra work.

Read article
Case studyComposite case9 min read

A spa chain goes digital, part 6: what this series teaches any multi-branch business

A retrospective on the whole series: the transferable method — pick the decision-data slice first, bind feedback at the right moment, and defer the sensitive systems until real data and trust exist.

Read article
Guide7 min read

Your website is live. Which basic numbers matter?

Four measurement groups give a new site a useful baseline: visits, sources, recorded engagement and enquiry actions. Here is what each can and cannot prove.

Read article
Explainer7 min read

Automation does not replace people on day one

Automation can reduce repetitive work and improve consistency, but a new workflow needs people to define, supervise and improve it before staffing assumptions can change.

Read article
Guide8 min read

Let real operations shape the next phase

The next system phase should be based on repeated evidence from customers and staff, not on the longest feature list imagined before the first workflow runs.

Read article