---
title: Services — TechJapan LLC
source: https://www.tech-japan.jp/services/
updated: 2026-09-20
facts: https://www.tech-japan.jp/facts.json
---
# The services, and what they cost.

Prices start at JPY 30,000, tax excluded, and every engagement is quoted in writing for an agreed scope before work starts — no setup fee. Ontology and AI integration start from that price; one kintone app, one automation or one small change to an existing system has a fixed price from JPY 50,000 before tax; larger kintone and offshore work is quoted per scope. The first consultation is free either way. Japanese IT and DX subsidies frequently apply and we help with the application.

## Pick by the problem, not by the technology

| If this is true | Start here | Price |
| --- | --- | --- |
| Retrieval returns confident, wrong answers and nobody can say why | [Ontology and knowledge graphs](https://www.tech-japan.jp/services/ontology/) | From JPY 30,000, per scope |
| A demo worked, and eight months later it is still a demo | AI integration | From JPY 30,000, per scope |
| Nobody finds the website except by name, and AI assistants describe the company wrongly or not at all | [Websites for search engines and AI](https://www.tech-japan.jp/services/ai-ready-web/) | From JPY 30,000, per scope |
| kintone holds the records, and paper still surrounds it | [kintone and AI](https://www.tech-japan.jp/services/kintone/) | Quoted per scope |
| You need sustained build capacity, not one more contractor | [Offshore development](https://www.tech-japan.jp/services/offshore/) | Quoted by team size |
| You want AI in your own operations but have no IT staff and do not want to start with a big system | [AI-accompanied development](https://www.tech-japan.jp/ja/ai-bansou/) (page in Japanese) | First consultation free; then from JPY 30,000 per scope |
| One process is still in Excel, or one system needs one more field, and the budget is small | [Small-scope development](https://www.tech-japan.jp/ja/small-dev/) (page in Japanese) | From JPY 50,000 before tax (JPY 55,000 tax included) |

## From a demo that impressed someone to a system nobody thinks about

Most AI projects do not fail. They stall — which is worse, because a stall consumes budget without ever producing a decision. The proof of concept succeeded, everyone agreed it was promising, and then it never crossed into anything anyone depends on.

The reason is almost always that the proof of concept was designed to succeed rather than to survive. It ran on an exported spreadsheet, one person operated it, and nobody had to be accountable for a wrong answer. Production has none of those affordances.

*Figure: The three phases of an AI integration engagement. Phase one is strategy: inventory, opportunity identification, ROI estimate, roadmap. Phase two is integration: build, deploy, connect, secure. Phase three is operation: monitor, improve, train, hand over. The exit condition is that the client team runs the system without us.*

```text
  +-------------+  +-------------+  +-------------+
  | 1 STRATEGY  |->| 2 INTEGRATE |->| 3 OPERATE   |
  +-------------+  +-------------+  +-------------+
    inventory        build            monitor      
    opportunity      deploy           improve      
    ROI estimate     connect          train        
    roadmap          secure           hand over    
                                          |        
                                          v        
                             you run it without us 
```

### Phase 1 — Strategy

An inventory of what operations and data actually exist, which is usually the first time anyone has written that down. Then: where AI could plausibly help, what an agent would need to be allowed to do, which use cases to attempt first, a defensible ROI estimate, and a roadmap. We also handle subsidy applications, because the paperwork is real work and it lowers your cost.

### Phase 2 — Integration

Building the thing: agent construction, generative AI integration, the data pipelines that keep it fed, deployment, API integration into the systems you already run, the interface, and the security and compliance work that a production system in Japan has to pass.

### Phase 3 — Operation

Monitoring so a regression is noticed by a graph rather than by a customer. An improvement cycle with a measurement attached. Training for the people who will own it. Then handover, on a date written down at the start.

> Phase 3 is the phase most engagements skip, and skipping it is how a vendor becomes permanent. The exit condition is in the scope document.

## What it costs

|  |  |
| --- | --- |
| Price | From JPY 30,000, tax excluded |
| How it is quoted | In writing, for an agreed scope, before work starts. The price holds for that scope |
| Setup fee | None |
| Additions | Work outside the agreed scope is explained and quoted before it begins. Nothing is billed without prior agreement |
| First consultation | Free, including the review of the current situation and a written scope |
| Subsidies | Japanese IT and DX subsidies often apply. Application support included |

A price for work whose scope is genuinely unknown at signing is a bet, and the vendor prices the bet in. So we do not quote the unknown. The first quote covers one small, clearly bounded piece of work; what comes after it is quoted once both sides have seen how the first piece went. You keep the right to stop at every boundary.

## Website production, closure and management

For businesses in and around Hadano, Kanagawa: website production and renewal from JPY 100,000, and closing down or taking over the management of an existing site from JPY 50,000. This is a local service and we are open about that. It exists because a surprising number of small companies are paying a monthly fee for a site nobody can log into any more.