Skip to content

DAVID GOVERNED SOFTWARE PRODUCTION

Turn ideas into applications.
Within your guardrails.

A dedicated environment for every application.
Build with your preferred agent, on infrastructure your organisation controls.

I WANT TO BUILD
a CRM dashboard.
Room for every ideaSix application environments sit on a shared David foundation. The selected application lifts above its own platform.SPACE / 01CRM dashboardSPACE / 02Customer portalSPACE / 03AI assistantSPACE / 04OperationsSPACE / 05ApprovalsSPACE / 06Your next ideaDAVID / SHARED FOUNDATION
01 / CRM DASHBOARD

A dedicated space for each idea. One governed foundation.

Infrastructure shouldn’t limit your imagination.

Let your people
explore like founders.

Your teams know where work gets stuck. Let them test solutions, with clear ownership and agreed limits.

01 / LEADERSHIP

Set the boundaries.

Choose priorities, data access and approved technologies.

02 / TEAMS

Make it tangible.

Own a problem. Work with an agent to build the first version.

03 / EVIDENCE

Learn before you scale.

Test with real users. Improve, adopt or retire.

AN INTELLIGENT PROCUREMENT PLATFORM

From briefing to a
working system.

For Melasan, five procurement mockups became one connected sourcing workflow in five working days.

Discuss a similar workflow

“What stood out in particular was how quickly the work was turned into tangible results, creating visible progress and momentum for the project.”

Niklas NiedristNiklas NiedristHead of Purchasing, Melasan

Frontira delivery case · July 2026 · 10 person days of work over five working days. A project example, not a delivery-time guarantee. Testimonial translated from German.

Choose a workflow.
See it in action.

Six examples, from internal tools to customer-facing products. Pick one and try the workflow.

Select an app to explore it at your own pace.

INTERNAL APPLICATION

I want to build
a CRM dashboard.

Bring customer context, opportunities and next actions into one place that matches the way your sales team works.

First useful workflow
From a new conversation to an owned next step.
Connects to
Customer records, email and your existing CRM.
What improves
Fewer missed follow-ups. A clearer pipeline.
Relationship OSILLUSTRATIVE EXAMPLE
Open opportunities24
Needs a next step03
NorthstarDiscovery
Oak StudioProposal
FieldworkReview

Give Northstar a clear next step.

Illustrative workflows, not packaged products or customer deployments. Each application is built for your situation.

From first version
to everyday use.

David prepares the environment. Your team and agent build. A named owner decides what goes live.

01 / PREPARE THE PROJECT

A home for the idea. Not another blank start.

Agree the first useful workflow, an owner and the account boundaries. Prepare the project with a repository, design standards and the services it needs.

THE HUMAN DECISION

Who owns it, who can access it, and what is it allowed to use?

RELATIONSHIP OSILLUSTRATIVE PROJECT

A clearer sales follow-up.

Internal application · Sales team

OwnerSales lead
First workflowConversation → next action
EnvironmentApproved project accounts
READY TO SHAPE

A focused outcome and explicit boundaries.

An explanation of the workflow, not a live project or product recording.

Built with an agent. Used by people or agents.
Those are different roles, with different access and operating responsibilities.

Explore the foundation ↘
The technical layers

Access: Colleagues, customers and partners use purpose-built applications. Coding agents work in the project repository.

Control: David connects project ownership, account boundaries, credentials and lifecycle. Forge can execute defined delivery tasks as a separate step.

Services: Source control, hosting, data, identity and models are selected for the agreed environment.

See the operator workspace
David operator workspace with project ownership and service status; identifying information is redacted
An existing David interface with demonstration data. Identifying information has been blurred.

Your guardrails.
Your stack.

You choose the services. We agree how they connect, where data lives and who operates them.

WHERE IT RUNS

Your cloud account.
Private infrastructure. Local.

HOW YOU BUILD

Your coding agent.
Your approved models.

HOW YOU KEEP CONTROL

Your identity, data policies
and operating requirements.

DAVID / ECOSYSTEM EXPLORER

Find the tools you already use.

Refine by service type 15 categories

32 featured / 76 possibilities

Select a logo to explore the setup

Services to explore, not a list of ready-made integrations. Scope and availability are agreed for your environment.

What these choices mean

Your cloud account can include Azure, AWS or Google Cloud. Open-weight describes model availability; local and private describe how inference runs. These choices can overlap.

Coding agents build applications. People and runtime agents use them. Their access, execution and operating responsibilities are scoped separately.

Deployment support, provider APIs, model compatibility, regions, costs and operational controls are confirmed during scoping.

Product names and marks belong to their respective owners. No partnership or endorsement is implied.

Start a conversation.
Not another form.

Give your agent a clear first task: define the users, workflow and smallest useful version before writing code. Copy this optional instruction to begin.

PROJECT DISCOVERY / AGENT INSTRUCTION
Read the agent instruction
We are working in a David project. First read the repository guidance, including AGENTS.md or CLAUDE.md if present.

Help me work out what to build before implementing it. Ask one or two questions at a time about:
• the outcome and who it is for;
• the main workflow and web or mobile needs;
• the data, integrations and access boundaries;
• the smallest useful version and how to test it.

Reflect back the scope, non-goals, constraints and open questions. Wait for my approval before implementing or creating execution tasks. Do not request secrets in chat.

A reusable conversation starter. This instruction does not connect to an agent or provision a project.

Get an independent second opinion

Independent second opinion

Put David under scrutiny.

These prompts explicitly ask your preferred AI assistant for evidence, open questions, and limits. That evaluates David as a product, not only Frontira as a delivery partner.

Opens an independent AI assistant. No partnership or endorsement is implied.

START WITH ONE REAL OPPORTUNITY

What would you
build first?

Bring one workflow and the systems it touches. We’ll help define a sensible first version.

Stefan Erschwendner

LET’S TALK

Stefan Erschwendner

Managing Partner · Frontira

Tell Stefan what you have in mind. Start with the users, systems and one useful workflow.

se@frontira.com

Opens an email draft with your selections. You review and send the message.

Prefer the contact form?

We reply within one business day to arrange the session.