aiwaka .
← All products

AIWAKA / KINTONE / PRODUCT DIRECTION

kintone AI Operations Administrator

Under development · Product direction

kintone administrators, business improvement leads, internal helpdesk staff: the roles businesses hire for guide what we want AI to do. This public product direction explores future coverage extending to sales administration and PMO work.

A working guide to the roles, duties, and keywords shaping AIWAKA’s future development.

Explore the six roles
AIWAKA ikebana logo
Start with the role you would hire for.

Design around recognizable hiring roles.

These six role families are future development targets. Their duties, keyword hypotheses, and envisioned agent outputs will guide the capabilities we develop and the connections between roles.

ROLE 01

kintone Administrator / Internal Systems Administrator

Work to cover
Maintain apps, users, organizations, and day-to-day operations—including work handled alongside general affairs or accounting.

Keyword hypotheses (Japanese market)
kintone管理者 (kintone administrator), kintone運用担当 (operations administrator), 社内システム管理 (internal systems administration), 総務 kintone / 経理 kintone (general affairs / accounting)

Envisioned agent outputs
App and permission inventories, account-change lists, configuration diffs, and operations reports.

ROLE 02

Business Improvement / DX Lead

Work to cover
Map business processes and take requirements through app development, changes, implementation, and ongoing improvement.

Keyword hypotheses (Japanese market)
業務改善担当 (business improvement specialist), DX推進担当 (DX lead), kintone 業務改善 (business improvement), kintone アプリ開発担当 (app developer)

Envisioned agent outputs
Process maps, requirements documents, app designs, code and configuration changes, and validation reports recording actual results.

ROLE 03

Internal Helpdesk

Work to cover
Handle kintone user questions, clarify usage issues and defects, and turn resolutions into better ongoing operations.

Keyword hypotheses (Japanese market)
社内ヘルプデスク (internal helpdesk), kintone 問い合わせ対応 (inquiry handling), 社内SE (internal systems engineer), kintone サポート担当 (support specialist)

Envisioned agent outputs
Ticket classifications, source-backed reply drafts, reproduction steps, escalation records, and FAQ improvement proposals.

ROLE 04

Documentation Specialist

Work to cover
Keep operating instructions aligned with app and workflow changes so users can carry out their work.

Keyword hypotheses (Japanese market)
マニュアル作成担当 (documentation specialist), kintone マニュアル作成 (manual creation), 操作手順書 (operating instructions), 社内ナレッジ整備 (internal knowledge management)

Envisioned agent outputs
Illustrated instructions, role-specific user guides, revision diffs, FAQs, and change-announcement drafts.

ROLE 05 / EXTENSION HYPOTHESIS

Sales / Sales Operations Administrator (kintone-related work)

Work to cover
Maintain customer, opportunity, and order information and connect sales activity to sales administration. This is a proposed extension of role coverage.

Keyword hypotheses (Japanese market)
営業事務 kintone (sales administration), 販売事務 kintone (sales operations administration), 受発注管理 (order management), 顧客管理担当 (customer data administrator)

Envisioned agent outputs
Proposed customer and opportunity updates, duplicate and missing-data lists, order summaries, and organized inputs for quotations and invoices.

ROLE 06 / EXTENSION HYPOTHESIS

PMO Assistant

Work to cover
Organize project progress, issues, and meeting information managed in kintone to support stakeholder decisions. This is a proposed extension of role coverage.

Keyword hypotheses (Japanese market)
PMOアシスタント (PMO assistant), プロジェクト事務 (project administrator), 進捗管理 kintone (progress tracking), 課題管理担当 (issue administrator)

Envisioned agent outputs
Meeting minutes, action lists with owners and deadlines, proposed issue-register updates, progress reports, and unresolved-question checklists.

Separate hiring language from outsourcing intent.

Role terms explore who a business wants to hire. Outsourcing terms explore which work it wants someone else to handle. A job posting is not evidence of search demand or buying intent.

  • Role vocabulary
    kintone administrator, business improvement / DX lead, internal helpdesk, documentation specialist, sales administrator, and PMO assistant.
  • Outsourcing-intent vocabulary (Japanese market)
    kintone運用代行 (outsourced operations) / kintone管理代行 (outsourced administration) / kintone保守 (maintenance) / kintone改修 (modifications) / kintoneアプリ開発 (app development) / kintone運用支援 (operations support).
  • These are unvalidated candidates, not measured search volumes or demand. Combinations of role, task, and outsourcing terms will help distinguish hiring, research, and purchasing intent.

From a role to everyday outputs.

This envisioned workflow connects each role’s duties from request intake through creating and applying the resulting work.

  • Receive work or a request → Identify the role and objective
  • Check the necessary information → Prepare app changes, replies, documents, or summaries
  • Validate and obtain required approval → Record the outcome and feed the next improvement

Job postings inform the vocabulary of work.

The Japanese postings reviewed describe kintone app operations and administration, user and organization management, improvement requirements, development and validation, user inquiries, and manual updates. Roles 01–04 synthesize that duty vocabulary. Combining administration with general affairs or accounting is an envisioned usage context.

Role 05, sales administration, and role 06, PMO assistance, are extension hypotheses for future validation—not roles directly established by this posting research. This is vocabulary research from a small sample, not evidence of market size, search demand, AI execution capability, or customer results.

Validate the language and buying intent. Expand role coverage.

Both the roles businesses want to hire and the work they want to outsource will shape development. Proving a small task is not the end goal: we will consider the connected duties needed across a role. Availability and implementation scope remain undecided.

DEVELOPMENT ROADMAP
  • 01Validate role language: compare postings, search expressions, and workplace terminology, then update the role-to-duty mapping.
  • 02Validate buying intent: distinguish hiring, information gathering, outsourced operations, and development requests; confirm the outputs buyers expect.
  • 03Expand role coverage: validate data, integrations, and execution quality for all six roles, then prioritize development including cross-department workflows.

We are exploring participation in Cybozu’s partner program; official certification has not yet been obtained.