Halaman studi kasus konstruksi dengan Claude Code: foto, jadwal, dan CTA estimasi

Halaman studi kasus konstruksi bisa punya foto before/after yang bagus, tetapi tetap gagal sebelum form estimasi. Pembaca ingin tahu scope, jadwal, survei lokasi, dan kategori biaya. Tindakan 30 menitnya adalah menaruh empat baris di atas CTA: foto, jadwal, rincian estimasi, dan input survei.

Artikel ini bukan pengganti review hukum. Claude Code membaca teks halaman, nama foto, catatan proyek, jadwal, item estimasi, dan field form, lalu mengeluarkan gap. Manusia memutuskan scope, harga, jadwal, kontrak, izin foto, dan publikasi.

Primary references used for the Japanese article: MLIT standard estimates, MLIT compliance guideline PDF, consumer FAQ about reform estimates, and MLIT law-change material. For the broader page structure, see construction case-study page workflow.

Poin utama

Put scope, process, estimate inputs, and site-survey requirements before the quote CTA.
Claude Code inventories page copy, photo names, schedule notes, estimate item names, and form fields.
Humans keep price, schedule, construction judgment, contract wording, photo permission, privacy, and publish approval.
Track quote-form start rate, site-survey booking rate, repeated questions, revision count, and review minutes.
The first action is one case page and one four-line table above the estimate CTA.

Di mana halaman proyek gagal

A reader checks project photos on a phone and compares them with their own wall, roof, shop, driveway, or room. Interest appears when the photo feels close. The page fails when the next step is unclear: which photos should be sent, which dimensions matter, whether a site visit is required, how long the work may take, and what cost categories will be reviewed.

The construction side has a different failure. Craft notes may mention protection, substrate repair, drying time, finish work, inspection, and cleanup. The published page says only that the work finished quickly. That makes the project look easy, then creates a mismatch during the estimate conversation.

Workflow: dari foto ke konsultasi estimasi

Review the case page in the visitor’s consultation order, not the company’s folder order. Put photo folder, craft note, schedule table, estimate item names, and form fields into one sheet.

Place	What to show	Human review
Before photos	problem, affected area, reason for inquiry	avoid photo-only diagnosis
Scope	area, part, material, excluded work	estimate premise
Schedule	protection, substrate, work, drying, inspection, cleanup	avoid unrealistically short schedule
Before estimate	photos, dimensions, desired timing, site survey, budget range	fewer repeat questions
CTA	quote consultation, reply timing, survey flow	less form anxiety

This table changes the prompt. Instead of asking for attractive copy, ask Claude Code to find missing scope, missing process, missing cost categories, and missing site-survey inputs.

Apa yang dilakukan Claude Code dan apa yang diputuskan manusia

Claude Code can classify photos, turn craft notes into headings, compare the schedule with the article sections, list missing estimate categories, inspect form labels, and flag vague claims. It can say that cleanup, safety cost, or photo permission is missing.

Humans decide construction scope, estimate assumptions, schedule, contract terms, safety, photo permission, customer privacy, and publication. Do not pass customer names, addresses, faces, license plates, nearby homes, or unapproved indoor photos to the model.

3 use case

Use case 1: Case page to estimate checklist

Input: case copy, Before/After photos, craft note, estimate items, form fields.
Output: table for problem, scope, process, result, and information needed before quote.
Human review: scope, price premise, construction judgment, photo permission, publish approval.

Use case 2: Schedule that does not overpromise

Input: process table, daily note, material, drying time, inspection item, cleanup task.
Output: process explanation separating protection, substrate, work, drying, inspection, cleanup.
Human review: site condition, weather, material delivery, attendance, neighborhood notes, contract schedule.

Use case 3: Estimate breakdown before CTA

Input: estimate item names, common questions, consultation form, reply email.
Output: plain explanation of material, labor, statutory welfare cost, safety cost, and site-dependent items.
Human review: actual estimate sheet, contract condition, project scope, wording for publication.

Prompt siap pakai

あなたは建設会社の施工事例ページ公開前レビュー担当です。
写真をきれいに見せるだけでなく、見積もり相談前の不安を減らす表を作ってください。

入力:
- 施工事例ページ本文
- Before / 工程 / After の写真一覧
- 職人メモ
- 工程表
- 見積書の項目名
- よくある見積もり前の質問
- CTAと問い合わせフォーム項目

確認してほしいこと:
1. 施工前の困りごと、工事範囲、工程、完成後の変化が同じ順番で見えるか
2. 見積もり前に必要な写真、寸法、現地調査、希望時期、予算感がCTA前にあるか
3. 材料費、労務費、法定福利費、安全衛生経費、建退共掛金など、見積内訳で人が確認する項目を表にする
4. 工期を短く見せすぎていないか。工程ごとの日数、養生、乾燥、検査、片付けが抜けていないか
5. 施主名、住所、顔、車のナンバー、近隣住宅、未許可写真が残っていないか
6. 人が確認する項目を、費用、工期、契約、写真許可、現地調査、公開承認に分ける
7. 今日30分で直す1箇所を1つだけ出す

制約:
- 工事金額、工期、法令判断を断定しない
- 存在しない資格、許可、工法、補助金を作らない
- 写真だけで施工品質を判断しない
- 不明な箇所は「要確認」とする

Kode pengecekan

This Node.js sample checks a small case-page object. It does not decide price, legal status, or construction quality. It only returns missing rows before publication.

const casePage = {
  title: "築32年戸建て 外壁補修と防水",
  photos: {
    before: ["crack-before.jpg"],
    process: ["sealant-work.jpg", "primer.jpg"],
    after: ["after-wall.jpg"],
  },
  estimateItems: ["材料費", "労務費", "法定福利費", "安全衛生経費"],
  scheduleItems: ["養生", "下地処理", "施工", "検査"],
  cta: "見積もり相談",
  privacyChecked: false,
};

const requiredEstimate = ["材料費", "労務費", "法定福利費", "安全衛生経費", "建退共掛金"];
const requiredSchedule = ["養生", "下地処理", "施工", "検査", "片付け"];

const warnings = [
  ...requiredEstimate
    .filter((item) => !casePage.estimateItems.includes(item))
    .map((item) => "見積内訳の確認項目が不足: " + item),
  ...requiredSchedule
    .filter((item) => !casePage.scheduleItems.includes(item))
    .map((item) => "工程説明が不足: " + item),
  ...(casePage.photos.before.length && casePage.photos.process.length && casePage.photos.after.length
    ? []
    : ["Before / 工程 / After の写真がそろっていません。"]),
  ...(casePage.cta === "見積もり相談" ? [] : ["主CTAが見積もり相談に絞られていません。"]),
  ...(casePage.privacyChecked ? [] : ["写真の掲載許可と写り込み確認が未完了です。"]),
];

console.log({
  canPublish: warnings.length === 0,
  warnings,
});

Pitfall: kesalahan umum

Failure	Cause	Fix
Only finished photo appears	visitor’s problem disappeared	show Before, process, After
Schedule looks too short	protection, drying, inspection omitted	show process names and review points
Estimate feels vague	no cost categories near CTA	explain material, labor, safety, welfare items
Unapproved photo remains	phone photo used directly	human checks signs, faces, cars, documents
Too many CTA buttons	phone, chat, document request, quote equal weight	make estimate consultation the main CTA

Pertanyaan umum

Q. Should the page show an approximate price? A. Only if a human confirms scope, included work, excluded work, and site condition. If price cannot be shown, explain cost categories instead.

Q. Can Claude Code decide schedule or price? A. No. It finds missing rows. People decide schedule and price from real site conditions.

Q. What photos are enough? A. Count is not enough. Check Before, process, After, permission, faces, license plates, and nearby homes.

Apa yang saya verifikasi

I checked slug, frontmatter, source links, internal link, CTA, code block, and final section for this article. The sample code reports missing construction-retirement-mutual-aid cost, missing cleanup, and unconfirmed photo permission. The first action is to pick one live case page and add photo, process, estimate breakdown, and site-survey inputs above the quote CTA. For team rollout, bring case URLs, photo lists, craft notes, schedule tables, and estimate item names to training dan konsultasi.