G2

Yurii L.

.NET Technology Lead

Information Technology and Services

Mid-Market (51-1000 emp.)

7/17/2026

"Process Management gave us structured approval flows without building another internal backend"

4.5/5

What do you like best about Kintone?

Kintone gave our operations team enough control to adjust forms, add fields, and refine views without turning every small request into a development ticket. That independence is useful, but we learned fairly quickly that no-code does not mean no governance. During the first few months, too many people had permission to change applications, and the result was predictable: duplicate fields, inconsistent naming, and formulas that only made sense to the person who created them. We eventually assigned an owner to each app, introduced conventions for field codes, and added a review step before changes reached production. Lookup and Related Records have been especially valuable when several workflows depend on the same information. Instead of copying the client, project, technical owner, and contract type into every new record, we pull those values from the source app and display linked requests, incidents, or deliveries inside the main record. To non-technical users, it feels like they are working in a single system. Underneath, we can still keep separate apps with cleaner responsibilities and avoid turning one giant form into the company’s entire operating model. Review collected by and hosted on G2.com.

What do you dislike about Kintone?

Kintone gives us enough visual flexibility for internal applications, but it starts showing its limits when the experience needs to feel highly tailored. Fields, groups, tables, and spacing are easy enough to arrange, but precise control over labels, responsive behavior, layouts, or interactive components usually means adding JavaScript, CSS, or a plug-in. We ran into that while building an app for field technicians. The team wanted every piece of information visible on a single screen so they would not have to move through tabs or extra steps, and we tried to accommodate it. The form technically worked, but it became dense, slower to scan, and harder to use on smaller screens. We spent some time trying to improve it with CSS before accepting that the problem was not the styling. The structure itself was overloaded. Simplifying the form and showing only the information technicians needed at each stage produced a much better result than continuing to decorate a layout that had already become too complicated. Review collected by and hosted on G2.com.

What problems is Kintone solving and how is that benefiting you?

A client integration required sandbox credentials, endpoints, technical contacts, API versions, test results, and several approvals before it could move into production. The issue was that all of this information was scattered across emails, support tickets, and a shared spreadsheet that two different people had already organized in completely different ways. We built an integrations app in Kintone and used Process Management to move each record through Discovery, Development, Client Testing, and Production Ready. Lookup pulled client data from our main app, and Related Records surfaced the incidents and deliverables tied to each integration. Our first version was too strict. We made so many fields mandatory that the team started entering placeholder values just to move a record forward. That technically satisfied the workflow, but it made the data less reliable. We adjusted the validation rules by status and added a JavaScript API customization that checked only the information required for each transition. Later, we connected the REST API to our deployment service so the release identifier and deployment result were written back to Kintone automatically. The platform didn’t remove the technical work, and it didn’t prevent us from designing a bad first version. What it changed was where that effort went. Instead of building and maintaining another internal application from scratch, we focused on the process, the validation logic, and the integrations that actually mattered. Engineering, QA, and operations ended up working from the same record, blockers became easier to spot, and we stopped asking the client for information that someone else on the team had already collected. Review collected by and hosted on G2.com.