SEEZ builds projects. We use AI at every step. We generate 1000 logos in minutes. We make the first selection, then show you our favourites.

Our motto is: Make it real first, improve it afterwards. We have more than 20 years of experience in software development and design. That has taught us that trying to be perfect from the start gets you nowhere. It only becomes perfect when you iterate quickly and keep making it better.

Built by SEEZ

rexlex : source-based Swiss legal AI for legal questions, document analysis, OCR, research, and letters.

Picorn : Design tool with a browser editor, AI images, and a large material library.

MomMirror : App for check-ins, reflection, goals, and personal insights in several languages.

bauKI : Jobsite app for voice, photos, and plan pins. It turns them into reports, punch lists, and PDFs.

What you can see in them

• RexLex: answers legal questions with sources, analyses documents with OCR, researches Swiss legal data, and helps draft letters.
• Picorn: AI creates images and design material right where it gets edited.
• MomMirror: AI turns short thoughts into patterns, goals, and next steps.
• bauKI: AI turns voice, photos, and plan markers into clean jobsite documentation.

Why this matters

Many companies ask the same question: what do we need AI for? The answer rarely sits in a strategy deck. It sits in daily work. In documents. In emails. In reports. In knowledge nobody can find. In tasks that come back every day.

If one of these projects feels close to your work, a call is worth it. Then we don't talk about AI as a trend. We talk about the workflow that eats time.

Look at the projects. If you have a similar problem, book a call.

AI is useful when it takes real work off the table. Not when it only writes nicer sentences.

The simple test: does someone have to read, search, sort, compare, summarize, write, or move information from one place to another? Then AI can probably help.

Simple AI use cases

• Read documents: summarize contracts, PDFs, reports, policies, or case files.
• Find knowledge: ask questions about internal documents and get answers with sources.
• Clean up speech: turn voice notes, meetings, or jobsite input into reports and tasks.
• Sort requests: pre-sort emails, forms, or customer requests.
• Pull out data: turn PDFs, forms, or tables into clear fields.
• Prepare content: draft texts, images, variants, or first versions faster.
• Prepare decisions: organize cases, documents, and data so people can decide faster.

What AI should not do

AI should not make hidden decisions. It should not hide responsibility. And it should not give an answer without a source when the source matters.

A good AI tool shows what it read, where it is unsure, and when a person needs to check.

The first step

Start small: one document type, one form, one team, one recurring task. Build a first version. Then you see whether the use case holds.

AI in real products

rexlex : shows how source-based legal AI works with document analysis, OCR, research, and Swiss legal data.

bauKI : shows how AI turns voice, photos, and plan pins into usable jobsite documentation.

If you can explain the workflow, we can check whether AI can remove work from it.

Behind SEEZ is one person who has been building software and digital products for more than twenty years. Those years shorten the path and skip a lot of discussions.

In the backpack: web apps, mobile apps, backend systems, data pipelines, and AI features — for enterprises, SMEs, startups, and own products. That breadth makes it faster to place a new project correctly and plan it realistically.

What experience changes

• Wrong directions get spotted earlier, before weeks of build time are lost.
• Complexity stays small, because it gets expensive later.
• Design, code, and AI hold together and get planned together.
• Architecture choices hold up, because I have seen how they behave after three years.
• Models, tools, and frameworks get chosen for fit — calmly, not at the pace of hype cycles.

Three disciplines, one person

At SEEZ there are no handoffs between strategy, design, and implementation. I understand the problem, design the interface, and write the code myself. That saves time, keeps the idea together, and removes misunderstandings between teams.

Experience with AI

AI is the most recent tool in a long line — not the first and not the last. That helps put it to use soberly: where it adds real value, where a simple script is enough, and where the process needs to change first.

Experience inside real products

rexlex : combines legal domain knowledge, RAG architecture, and Swiss legal data into a usable tool.

bauKI : turns sentences spoken straight into the phone on the jobsite into structured items — defects, completed tasks, and report entries.

Experience shows in the end through decisions that still hold up a few weeks later.

SEEZ connects product thinking, design, AI, and code. The goal is a first version people can use.

I work where companies need clarity fast: can this idea work? Can AI take work away here? What would the first usable tool look like?

Concrete services

• AI prototypes: first versions for ideas that should not stay in meetings.
• Internal web tools: tools for teams, approvals, data, and daily work.
• Automations: workflows that prepare documents, emails, speech, forms, or raw data.
• Knowledge search: ask internal documents questions and get answers with sources.
• Interfaces: screens and tools that make AI understandable, checkable, and usable.
• First product versions: digital products that reach real users early.

What you get

Not a concept as the final deliverable. You get a next step: a clear use case, a clickable prototype, a working flow, or a first product.

How SEEZ works

Direct, small, close to the problem. You bring domain knowledge and reality. I bring structure, design, AI, and implementation. Together we first build the thing that tests the path.

Services inside products

rexlex : connects SvelteKit, FastAPI/RAG, Swiss legal data, credits, and encrypted storage in a usable legal tool.

bauKI : connects a mobile web app, voice, photos, plan pins, offline sync, and finished PDFs.

Do not start with a feature list. Start with the problem.

A good project starts with a clear conversation: what happens today, what costs time, who is affected, what should get easier?

After that, we build small. We do not plan for months. A first version shows faster whether the idea works in daily use.

The process

• 1. Call: We spend 30 minutes on the problem, goal, and context.
• 2. Clarity: We separate good AI use cases from ideas that only sound complicated.
• 3. Scope: We choose the smallest useful first use case.
• 4. Prototype: SEEZ builds a first version with interface, logic, and realistic flow.
• 5. Test: The system is checked with real input, real people, or real data.
• 6. Decision: What works gets built out. What does not work gets changed or stopped.

Why start small

With AI, many problems only show up in use: wrong expectations, unclear sources, bad inputs, missing approvals. A prototype shows these things early.

A good first step

A good first step is concrete: one document type, one team, one form, one workflow, one dashboard, one customer process, or one product core.

Not: "We want AI." Instead: "This workflow needs to get better."

What is clear afterwards

You know whether the use case holds, what needs to be built, where the risks are, and whether the next step is worth it.

How real products start

bauKI : started with a clear problem: jobsite documentation had to get faster and cleaner.

rexlex : started with a clear legal problem: sources, documents, OCR, research, and letters need one workspace.

Picorn : started with a product flow: search, create, edit, and reuse material.

The next step does not need to be big. It needs to be concrete.

The simplest next step is a call. You explain the problem, idea, or workflow. I tell you honestly whether AI can help.

You talk directly to Simon. No consulting machine. No handoffs. No split between strategy, design, and implementation. I understand the process, design the interface, and write the code.

When a call is useful

• A workflow takes too much manual work.
• You are asking whether AI makes sense in your company.
• You have a product idea and want to see a first version quickly.
• You have documents, knowledge, or data that are hard to use.
• You want to talk to the person who builds.

What to bring

One example is enough: a form, a document, today's workflow, a recurring task, or a product idea. It does not need to be perfectly prepared. It needs to be real.

What you know afterwards

After the call, three things are clearer: whether AI makes sense, which first use case is realistic, and what a first prototype could look like.

Why SEEZ

I built RexLex, Picorn, MomMirror, and bauKI. These products shape how SEEZ works: fast, direct, concrete, and close to real use.

Book the call. After that, we both know whether a project makes sense.

Operator

SEEZ: Simon Siegenthaler
Switzerland
Email: [email protected]
Web: seez.ch

Responsible for content

Simon Siegenthaler is responsible for the content on this website.

Liability

I prepare the content carefully. Still, I cannot guarantee that everything is always complete, correct, and up to date. Liability claims caused by use or non-use of this website are excluded where the law allows it.

External links

This website links to external websites. Their operators are responsible for their content.

Copyright

Text, images, graphics, and code on this website are protected. Please do not copy or reuse them without permission.

Controller

SEEZ: Simon Siegenthaler, Switzerland.
Privacy questions: [email protected].

Principle

This website processes as little personal data as possible. No tracking, no advertising, no third-party cookies.

Server logs

When you open the website, the hosting provider stores technical data in server logs, for example IP address, date, requested URL, and browser identifier. This data is used for operation, security, and error analysis and is deleted after a short time.

Contact

If you contact me by email or Calendly, I use your details only for the request and the appointment. This can include name, email, message, and requested appointment time. The data is not passed on to third parties.

Calendly

Appointments are booked through Calendly. When you open the booking page, Calendly's privacy policy applies.

Cookies and local storage

This website sets no tracking cookies. Technical values, for example the selected language, can be stored in the browser's localStorage.

Your rights

You have the right to access, correct, delete, and restrict processing of your data. Write to [email protected].

Changes

This statement may change when technology or legal requirements change. The version published here applies.