Skip to content

Papers

The thinking is written down before the code is.

Every large piece of work starts as a document: what is known, what the options are, what was chosen and why. These are 30 of them, with a short summary of each.

The full documents stay in their private repositories because some contain internal pricing or contact details. Any of them can be shared on request.

  • Research · 10
  • Architecture · 6
  • Design · 9
  • Decision record · 1
  • Plan · 4

Studio R7

Agency website, free apps and client platform

  • Research393 lines

    Answer engines and structured data

    How AI assistants and search engines read a small-business site in 2026, what changed when FAQ rich results were withdrawn, and the checks added to the build as a result.

  • Research315 lines

    Site SEO audit

    A page-by-page audit of 84 pages: titles, descriptions, canonical and language tags, structured data, and what to fix first.

  • Architecture153 lines

    The engine bible

    The 36 building blocks of the growth engine, the rules they follow, the decisions already made and the 17 tensions still open.

  • Architecture139 lines

    Dependency map of the 36 blocks

    What must exist before each block can be built, and the order of the stages that follows from it.

  • Architecture37 files, 420 to 980 lines each

    Component dossiers C01 to C36

    One dossier per block: the options compared, the choice and why, the cost model, and sources. Examples: event spine, AI router, cost ledger, page quality check.

  • Design550 lines

    Quality standard

    A 1-to-5 scale across 14 dimensions, three scorecards, and the gate a piece of work must pass before it ships.

  • Design277 lines, plus a 288-line review

    Client back end design

    The client portal: who sees what, the data model, the security model, and every screen in both languages.

Dee Wan Nee

Restaurant deals and discovery platform, inside LINE

  • Research1,145 lines, plus a 318-line source appendix

    Will this deal pay? The deal-value calculator

    The maths of a restaurant discount: when a deal fills a table profitably and when it gives margin away, turned into a planner with exact arithmetic and known-answer tests.

  • Research636 lines

    Career timelines for chefs

    How to show a cook's career so it is true: who confirms each entry, what counts as evidence, and how other professions solve it.

  • Research210 lines

    Chef and sommelier profiles

    What a profile needs to be useful to a diner, an employer and the person it describes.

  • Research79 lines

    Verifying a business

    How to check that the person claiming a restaurant really runs it, using Thai business papers and an ID, with a person making the final call.

  • Decision record20 to 105 lines each

    Nine architecture decision records

    LINE login mapped to database sessions, threshold deals with a fixed fee, reward units and their ledger, the creator programme, more ways to sign in, and one fee table.

  • Architecture323 and 303 lines

    System overview and database design

    How the public site, the LINE apps, the admin console and the database fit together, and the shape of every table.

  • Plan1,290 lines

    Palate build plan

    The full plan for career profiles: data model, flows for cooks and restaurants, the accreditation registry and the release steps.

  • Design9 documents

    Design system: look, patterns, characters, governance

    How the app should look and behave, the rules protecting the character art, and who may change what.

PaiTor

Free used-car listing tool, and PaiTor Pro for car yards

  • Research431 lines

    Trust badges and verification

    What a marketplace may honestly claim about a seller or a car. The conclusion became a product rule: never say "verified" unless something was checked.

  • Research185 lines

    Finding a car: browse and search

    How buyers actually look for a used car, and a build plan for filters, saved cars, compare and returning to the same place.

  • Research904 lines

    Chat architecture

    Options for buyer-and-seller chat compared on cost, reliability and abuse, with the design chosen and how it is tested under load.

  • Plan921 lines

    Search alerts and offers

    Saved searches, daily alerts, price history and offers, from the data model to the message a buyer receives.

  • Plan735 lines

    Dealer growth and stock sync

    How a car yard claims its page, keeps stock in step from a spreadsheet or LINE, and what keeps listings fresh.

  • Research26 documents, about 9,400 lines

    The research library

    Four questions, each researched three times and then combined: dealer stock sync, the money model, ranking, and growth. Stored in the product's own database for reuse.

  • Design3 documents, 216 lines, with 36 working mock-ups

    Dealer back office specification

    "The office" and "the lot": two experiences for one dealer, every screen and state, and how paid placement is labelled.

  • Design510 and 301 lines

    Brand story and cast

    The world of the soi, the seventeen characters, how they speak, and the rules for what they may never do.

  • Design287 lines

    Quality pass

    A screenshot audit of every page at two widths in three languages, with each finding and its fix.

RevIQ

Business suite for Thai vendors and small companies

  • Architecture1,126 lines

    Architecture v2

    The foundation for the rebuild: the workspace model, channel adapters for LINE, WhatsApp and email, and the decision engine.

  • Architecture134 lines

    Entitlements

    How plans and features are gated from one place, and how that closes the loop with billing.

  • Design205 lines

    Theme architecture

    Design tokens, presets and safely scoped custom styles, so each storefront can look like its own brand.

  • Design3 documents, 389 lines

    SignIQ composer and send-to-sign

    The agreement composer, how a document goes out for signature, and what the signer sees.

  • Plan388 lines

    LeadIQ engine plan

    Scoring, nurture plans and replies that are planned, written and then checked before they are sent.

  • Design514 lines

    Form builder redesign

    A user-experience review of the form builder and the redesign that followed.