"FDE" Articles (19) | TIMEWELL Inc.

When a VC Goes Forward-Deployed: What It Means and How Founders Should Vet It

In October 2026, US venture capital firm Theory Ventures described its "Forward Deployment" approach, in which it embeds people in portfolio companies to help build sales and hiring. This article separates what has been published from what rests on the firm's own account, and sets out what it means for a VC to move from advice to execution, and five points a founder should check beforehand.

2026-10-21Ryuta Hamamoto

WARP

Running Business Apps in Your Own Cloud Tenant: Access, Data Location, and Personal Data

If you are dropping a SaaS product and building the business app yourself, my view is that it usually runs better inside your own cloud environment, your own tenant. The fifth and final article in this series covers how that differs from multi-tenant SaaS, what you gain in identity, access, data integration, and audit logs, why "who can touch the data" rather than where it sits decides whether Japan's APPI treats a vendor as an entrusted party, why choosing a Tokyo region does not remove the duty to understand foreign rules, and how operational responsibility shifts to you. It draws on NIST, AWS, the Japanese Personal Information Protection Commission's Q&A and the 2026 APPI amendment, and ISO/IEC 27001.

2026-09-29Ryuta Hamamoto

WARP

How to Cancel a SaaS and Migrate Off It: Notice Deadlines, Data Export, and Parallel Runs

Once you decide to cancel a SaaS and build the replacement in-house, plan backward from the renewal date. This article covers the notice deadline for stopping auto-renewal, the clause that re-prices a renewal when you cut seats, the 30-day window to export data after termination, narrowing what you migrate, and deciding in advance when a parallel run ends. It draws on guidance from Japan's IPA, the Japan Fair Trade Commission, the Digital Agency's DS-310, the Japanese Civil Code on standard terms, and the EU Data Act, and ends with a schedule worked back from the renewal date.

2026-09-29Ryuta Hamamoto

WARP

Should You Cancel Your Expensive SaaS and Build It Yourself? Seven Tests for the AI Era

For IT heads, corporate planning teams, and CFOs who opened a SaaS renewal quote and thought "we could build this for less," here are seven tests for deciding whether to cancel a SaaS you already pay for and build a replacement in-house: price increases and currency exposure, per-seat pricing growth, how slowly the data and features change, legal and accounting complexity, the number of integrations, who will maintain it, and the cancellation and migration terms. It does not hide the evidence on the other side, including public guidance that favors SaaS and research showing AI-assisted development can be less stable. The first article in a five-part series.

2026-09-29Ryuta Hamamoto

WARP

Five-Year SaaS TCO | How Price Hikes and a Weak Yen Move the Build-vs-Buy Break-Even

When a SaaS renewal quote makes you think building it yourself would be cheaper, the number to put in the approval request is a five-year total, not the annual fee next to a development estimate. Using the actual track record of vendor price increases and the weak yen, and the lifecycle-cost principle in Japan's Digital Agency guideline DS-310, this article works through a model case of a Japanese company (300 users, $60 a month, ¥160 to the dollar, all our own assumptions) with maintenance, security, and people included, and tables the variables that move the break-even point.

2026-09-29Ryuta Hamamoto

WARP

Which Business Systems Can You Build Yourself? Sort Them by How Often the Data Changes

Internal FAQs, ledgers, and intranet portals rarely change their data, and with generative AI they have become realistic to build and own yourself. But read plainly, Gartner's pace-layered model says the opposite: slow-changing systems of record belong on standard packages. This article adds a second axis, weight (complexity, volume, and regulation), sorts business functions into four groups, and gives a quick-reference table showing what to build and what, like accounting and payroll, should stay on SaaS.

2026-09-29Ryuta Hamamoto

WARP

FDEs and Business Ethnography | Turning What a Workplace Takes for Granted into Product

Observation methods capture what people do. Ethnography captures why, in that group, it is taken for granted. The third article in our FDE practice series traces how an anthropological method reached corporate workplaces by way of Xerox PARC, explains Polanyi's tacit knowledge and Nonaka's socialization, shows how to write thick description, and lays out how ethnography differs from observation and why an FDE spends weeks on site. Contract-development business analysis targets "the process"; FDE ethnography targets "what this company takes for granted" and turns what it learns into standard product features. It also covers the time-boxing and deliverables that keep this from becoming live-in contract work.

2026-09-15Ryuta Hamamoto

WARP

Filming the Shop Floor and Analyzing It with AI | Consent, Camera Setup, and the Analysis Pattern

Our engineers have started filming work on site, with permission, and analyzing the footage afterward with AI. Where observation means seeing things once, in the moment, video means seeing them again as many times as needed, and it captures what the eye cannot count well, such as the exact length of a wait or the number of screen switches. The fifth article in our FDE practice series covers how to obtain consent, the essentials of Japan's personal-data law and the camera-image guidebook, when to use a fixed camera versus screen recording, the boundary between what AI analyzes and what people keep, and how this differs from work analysis in contract engagements. FDE video analysis ends when the footage has become next week's working artifact.

2026-09-15Ryuta Hamamoto

WARP

The Interview Skills That Make an FDE Work | How to Draw Real Insight Out of the Shop Floor

Whether a Forward Deployed Engineer succeeds is decided less by how fast they write code than by how they listen. Our engineers take interview training before they go on site, but the "form" you learn in training and the "eye for mismatch" you only develop in the field turned out to be different things. This article lays out the three kinds of FDE interviews, question design built on the critical incident technique and Toyota's five whys, silence and mirroring, working in pairs, and where AI transcription fits, in a form engineers can use as is.

2026-09-15Ryuta Hamamoto

WARP

FDEs and the KJ Method | Turning Field Fragments into Structure, and Where AI Stops

The fragments collected through interviews, observation, and ethnography cannot be used for implementation as they are. To turn fragments into structure, our engineers use the thinking behind the KJ method, which the anthropologist Jiro Kawakita created for field research. The fourth article in our FDE practice series walks through the steps, one idea per card, gathering by meaning, diagramming, and writing up, using real field notes as material. It covers the boundary between what AI does and what people keep, how this differs from requirements consolidation in contract development, and how the structured result feeds the next week's implementation. The KJ method is a registered trademark of Kawakita Research Institute, which provides formal training.

2026-09-15Ryuta Hamamoto

WARP

Why the FDE Market Exploded | 2026 in the Numbers on Jobs, Investment, Acquisitions, and Results

Job postings for Forward Deployed Engineers rose 5,230 percent between January 2025 and April 2026 on Indeed data. OpenAI launched a deployment company with more than $4 billion, AWS committed $1 billion, Anthropic set up a mid-market company with investment firms, and Palantir posted 93 percent revenue growth with a 47 percent operating margin in the second quarter of 2026. The eighth article in our FDE practice series reads why this role expanded so sharply from 2025 to 2026, through primary-source numbers on jobs, investment, acquisitions, and results, and then covers what the numbers do not say: how to tell a real FDE from a relabeled contractor.

2026-09-15Ryuta Hamamoto

WARP

How FDEs Observe | Shadowing and Contextual Inquiry to Catch the Steps Nobody Explains

Interviews get you half of how work is actually done. The other half sits in steps the people doing the work cannot explain, and only observation catches it. The second article in our FDE practice series lays out three observation methods, shadowing, contextual inquiry, and think-aloud, down to when to use each, where to sit, what to watch, and what to write. It covers Taiichi Ohno's chalk circle, how to handle the Hawthorne effect, how FDE observation differs from the as-is analysis in contract development, the FDE habit of putting a working artifact down the day after observing, and four patterns we keep finding on shop floors.

2026-09-15Ryuta Hamamoto