Set the boundaries.
Choose priorities, data access and approved technologies.
DAVID GOVERNED SOFTWARE PRODUCTION
A dedicated environment for every application.
Build with your preferred agent, on infrastructure your organisation controls.
A dedicated space for each idea. One governed foundation.
Infrastructure shouldn’t limit your imagination.
Your teams know where work gets stuck. Let them test solutions, with clear ownership and agreed limits.
Choose priorities, data access and approved technologies.
Own a problem. Work with an agent to build the first version.
Test with real users. Improve, adopt or retire.
AN INTELLIGENT PROCUREMENT PLATFORM
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 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.
Six examples, from internal tools to customer-facing products. Pick one and try the workflow.
INTERNAL APPLICATION
Bring customer context, opportunities and next actions into one place that matches the way your sales team works.
Give Northstar a clear next step.
Illustrative workflows, not packaged products or customer deployments. Each application is built for your situation.
David prepares the environment. Your team and agent build. A named owner decides what goes live.
01 / PREPARE THE PROJECT
Agree the first useful workflow, an owner and the account boundaries. Prepare the project with a repository, design standards and the services it needs.
Who owns it, who can access it, and what is it allowed to use?
Internal application · Sales team
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.
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.

You choose the services. We agree how they connect, where data lives and who operates them.
Your cloud account.
Private infrastructure. Local.
Your coding agent.
Your approved models.
Your identity, data policies
and operating requirements.
32 featured / 76 possibilities
Select a logo to explore the setupServices to explore, not a list of ready-made integrations. Scope and availability are agreed for your environment.
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.
Give your agent a clear first task: define the users, workflow and smallest useful version before writing code. Copy this optional instruction to begin.
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.
Independent second opinion
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
Bring one workflow and the systems it touches. We’ll help define a sensible first version.

LET’S TALK
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.