Temotoku Additional Development
Estimate Preconditions

• Front-end UI (HTML/CSS) has been built by CTN. Front-end design and coding is out of scope.
• Admin panel (store data entry screens) has been built by CTN. Admin panel UI development is out of scope.
• Store information API is assumed to already be built. Only the connection to the front-end will be developed. If new API construction is required, a separate estimate will be provided.
• Vehicle data integration (Extreme → CTN server) is assumed to have been completed manually by CTN. We will only reference data already imported into the CTN database.
• Vehicle data import into the CTN database is also assumed to have been completed manually by CTN. Development of the import process is out of scope.
• Store-to-vehicle linking uses a composite key of Company ID + Store ID. It is assumed this structure already exists in the database.
• Vehicle data is assumed to be updated via daily CSV batch sync at 00:00. Real-time sync is out of scope.
• Additional development will be built on the existing Temotoku architecture and tech stack. No tech stack changes or major refactoring are included.
• Front-end UI, API, and infrastructure/DB are existing deliverables. Work scope is limited to wiring screen display via API + adding ad measurement & source tracking screens/API only.
• API specification document is assumed to be finalized with all required items covered. Any deficiencies or changes will require a separate estimate.
• Bug fixes in the API itself will be proposed by us and developed upon mutual agreement. Test environment and data are assumed to be provided.
• Development is based on Figma designs and the beta site. Modifications or additional screens will be discussed separately.
• SEO specification sheet (page titles, canonical tags, indexing targets, etc.) will be shared separately by CTN. Work cannot begin if specifications are not finalized.
• Existing repository, development environment, and access permissions are assumed to be provided.

Page Structure

• 3-level hierarchy: Prefecture selection page → Store list page → Store detail page
• Prefectures with 0 stores will have disabled links (no navigation)

Store Information (Scope)

• Display only. Retrieve store information from API and display on front-end.
• Display covers normal cases + zero-result handling only. Other error cases will be addressed as needed.
• Create, update, and delete are out of scope — handled in CTN's admin panel.

Store Search (Scope)

• Retrieve and display prefecture-based store lists from API
• Retrieve and display individual store detail information from API
• Display vehicle inventory list linked by Company ID + Store ID

Display Items

• Store detail page will only include items shown in the Figma design or beta site.
• Adding items not in the Figma design will require a separate estimate.

Data Updates

• Data update mechanisms (store registration sync, daily vehicle update at 03:00) use existing API. Building integration infrastructure is not included.

Page Navigation

• Navigation link from vehicle detail page → store detail page. Link placement and design follow Figma.
• Navigation from store detail page vehicles → vehicle detail page (connection to existing pages).

• Structured data, breadcrumbs, title tags, and canonical settings for store-related pages (search, list, detail).
• Detailed specifications will be shared separately by CTN via a specification sheet. Work cannot begin if specifications are not finalized.

Parameter Tracking

• Capture URL parameters (ad company, media, identifier, campaign ID) from ad-driven traffic.
• Persist parameters via Cookie/session throughout same-domain navigation (tracked until inquiry completion = thank-you page).
• Parameter specifications (key names, value formats, etc.) are defined by CTN.
• Save parameter data to database upon inquiry submission.
• Implement the same parameter tracking system as the vehicle purchase (Kaitori) site.

Billing Model

Two billing models will be implemented:

• Performance-based pricing (inquiry unit price, contract unit price) is also set in CTN's admin panel. Payment processing and invoicing features are not included.

Inquiry Management (Scope)

• Inquiry completion email is already implemented. Ad source parameter data (ad company, etc.) will be added to the email body.

Ad Company Admin Panel (Scope)

• Customer personal information is not viewable by ad companies (vehicle information is viewable).
• Specifications (fee rates, matching rules, attribution, account issuance, contract button, CSV/monthly definitions) are assumed to be finalized within expected scope. Additional complexity will require a separate estimate.

• Front-end page UI/design development (already built)
• Admin panel UI development (already built)
• CSV data integration from Extreme (core ERP system) — assumed to be handled manually by CTN
• Vehicle data import into CTN database — assumed to be handled manually by CTN
• B2B site (Mobitech) development
• Vehicle search / vehicle detail page modifications (already completed)
• Payment, invoicing, and payment management features
• Server and infrastructure setup / operations

• This estimate is a rough estimate based on the API specification document and Figma designs. If specification changes occur after development begins, additional costs may apply.
• If any of the above preconditions change, the estimate amount and timeline may be adjusted.
• Post-release defect support scope will be determined separately.