How we work

AI in our development.

We use AI in every step of our work. The decisions stay with people; tools take over the routine work.

Support, not replacement.

Our developers have decades of FileMaker experience. AI doesn't replace them. It takes over what eats time and needs no experience: writing minutes, running through test cases, keeping documentation current, trying out variants.

What remains is the part you hire us for: understanding your processes and translating them into software that fits your workflows. Every result a tool produces is reviewed by a person before it is used.

Script: Close order Created by AI
Set Error Capture [On]
If [ IsEmpty ( Order::DeliveryDate ) ]
Show Custom Dialog ["Delivery date missing"]
Exit Script [False]
End If
Set Field [ Order::Status ; "closed" ]
Commit Records/Requests
Developer review: checked and approved
Agentic development
AI builds with us - directly in FileMaker.

Agentic development means: AI coding environments such as Claude Code, Cursor, or Codex work as part of the team. The agent plans, builds, and checks in traceable steps; every result is approved by our developers. Claris is deliberately extending FileMaker for these tools. For us, this way of working is everyday practice. Where a tool is missing, we build it ourselves.

Scripts & schema

The agent knows the solution's structure and FileMaker's scripting language. We describe the logic; it writes production-ready scripts directly into the file - supervised, with review.

Modern user interfaces

Web-native interfaces emerge in dialogue with the agent and run in the web viewer of your FileMaker app - protected by your existing access privileges.

FileMaker stays the core

Data storage, privileges, logic, and operation stay on the platform that carries your solution. The agent speeds up the build; FileMaker executes.

A structured process. The agent works in a structured, repeatable process with tests and review - not on shouted instructions.
In daily work
Where AI takes work off our hands every day.
From conversation to prototype

With your consent, we record conversations. From the transcript come the minutes and a clickable prototype - you see your future application before a single line of code is written.

Automated tests

Every feature gets test cases before you see it. Regressions - errors triggered by a change somewhere else - surface before delivery, not after.

Debugging & review

AI tools read code and script logic across the board and find patterns and inconsistencies that get lost in daily work. Decisions are made in review, by people.

Documentation that stays current

Technical documentation and manuals are maintained with every version - as part of the delivery, not as an afterthought.

No longer limited to what FileMaker can do.

FileMaker remains our platform: data storage, privileges, logic, security, guaranteed compatibility. But the user interface is no longer bound to the platform's limits.

Where a FileMaker interface reaches its limits, we keep building with modern web technology - directly in the web viewer, the built-in browser window of every FileMaker app, or as a standalone web application in the browser. Underneath, in both cases, runs your FileMaker Server, accessed through its official interfaces. No second database, no second privilege system, no synchronization. Operated in our Swiss data center, together with your database.

That is what distinguishes our web applications from what you get when you tell an AI: «Build me an app.» Data model, privileges, backups, encryption, operation, updates - all questions that must be answered in an enterprise environment. With us they are, because the answer is FileMaker Server, and we have been operating it since 2014.

If you ask «Can FileMaker do that?», the answer is almost always yes.

ONE DATABASE · ONE PRIVILEGE MODEL · NO SYNCHRONIZATION
FileMaker Pro
with web viewer
Web app in the layout
Browser
Desktop & mobile
Standalone web app
FileMaker Server
Official interfaces (Data API) · Data storage · Privileges · Logic
Operated in Innodat's Swiss data center
What goes to AI tools and what does not.

We use AI-supported tools in analysis, design, programming, testing, and documentation. Their use is limited by these rules:

1

What goes to the tools: schema, structure, calculations, script logic, and program code without data content, plus synthetic - that is, artificially generated - test data.

2

Your records, extracts, screenshots containing data, log files, and error messages with data values do not leave Innodat. Our clients' personal data is never transmitted to external AI services.

3

Using tools changes nothing about responsibility. Innodat professionally reviews every generated result before it is used.

4

You can prohibit their use in writing at any time. Innodat will lay out the impact on schedule and price beforehand.

We work on our own working copy with synthetic or anonymized test data. Processing takes place in Switzerland. For the processing of personal data, a data processing agreement under the Swiss Data Protection Act (DSG) applies.

From the blog
Examples from our work with AI.
AI Development with FileMaker · June 10, 2026
What We're Building, and Why Not the Built-In RAG

The target system, what you need to build along, and how the AI-assisted way of working functions.

AI Development with FileMaker · June 17, 2026
Giving the AI Knowledge of Your Solution: The DDR

The Database Design Report as the AI's knowledge base - and the free tool that prepares it.

AI Development with FileMaker · July 29, 2026
Ingestion I: From Document to Chunks

The first server-side script, the first AI-generated external service - and the empty-variables trap.

All posts  →
Interested in the added value Innodat's way of working can generate for you?
Free initial consultation