How we work

Built with AI.Handed over.Yours to keep developing.

On the right architecture, you change your app by describing the change.

A team of experienced AI architects builds your app. We hand it over with everything your team needs to keep developing it, train them to do it, and stay available whenever you need us.

Talk through your use case30 minutes, free of charge
Your team, in your app

Quotes with a discount above the agreed limit need approval from the regional sales manager.

  1. Reads the documented structure and past decisions
  2. Adds an approval step to the quote process
  3. Updates the quote screen and the routing rule
  4. Runs the automated tests
  5. Ready for your review
Quote with discount above limitWaiting for the regional sales manager
ApproveEditReject
Salesforce partner since 2018Our own apps in daily useFrankfurt · Portugal · USA
We work this way ourselves

166 of 169 changes merged into the baucore.app website since March 2026 were written by AI and reviewed by an architect.

Baucore (built by IBS, now an independent company), SalesExt and MyDocGen are built and developed the same way.

What you receive

A handover you can open and read

Seven things come with every offer. They are what a new developer would need, and AI tools depend on them even more. On Salesforce it lives in your org and your repository. On your own stack it runs on your infrastructure.

01

Source code and full ownership

All source code lives in your own repository. No licensing dependency on IBS.

02

Architecture documentation

Structure, data model and interfaces, written down. It is the first thing an AI tool reads before it changes anything.

03

Decision records

Why the app was built the way it was, so neither a new developer nor an AI undoes a decision by accident.

04

Automated tests

A test suite that shows at once whether a change broke something, whether a person or an AI made it.

05

Deployment and environments

A setup your team can use to test and release changes without us.

06

Training to develop with AI

Your team learns the workflow on your own app. They describe changes, review what the AI built and release it. Delivered by the architects who built it.

07

A clear split of work

You decide what your team builds and what you bring back to us. Either way, we are available on request.

Your repositoryExample
  • your-app/
  • README.mdhow to run it and where to start
  • docs/
  • architecture/structure, data model, interfaces
  • decisions/why it was built this way
  • src/the app, in your repository
  • tests/runs on every change
  • deploy/environments and release steps

docs/decisions/0007-discount-approval.md

Status
Accepted
Context
Discount approvals were handled by email and left no record.
Decision
Quotes above the limit go to the regional sales manager for approval inside the app.
Result
The limit is one setting. Changing the rule means changing the tests first.
The path

From first call to your team in charge

You see working software early and finish with an app your own team can change.

01

First call

You describe the use case. We tell you whether it is a Baucore case, a Salesforce case or a case for your own app, and whether it is worth building at all.

30 minutes, free
02

Blueprint

We write down what gets built, where and in what order, together with the people who run the process. Fixed scope, fixed fee, fixed end date.

Fixed end date
03

Build

Architects direct AI to build your app. You review running software early and steer while changes are still cheap.

Working software within weeks
04

Hand over

Code, documentation, decision records and tests go into your own repository. We train your team on your own app.

Yours to develop
05

Stay

A new integration, a larger change or a plain question. We are available on request.

Whenever you need us

At the end you hold a blueprint

What gets built, where and in what order. It is yours, even if you give it to someone else. Sometimes the recommendation is to build nothing, and then it says so.

If we build, the fee is credited

The blueprint fee is credited against the build.

After go-live

Your team

With AI, day to day

Your people who know the process can make these changes. Developers are optional.

  • New fields, screens, reports and rules, described and reviewed with AI
  • Day-to-day operation and user management
  • Content and master data
  • Routine troubleshooting

IBS

Whenever you need us

The work that needs an architect, plus answers to your questions.

  • New interfaces and connected systems
  • Structural and architectural changes
  • Architecture reviews and larger initiatives
  • Training for new team members
  • Questions, on request
Why it works

AI is only as good as the architecture it works on. Point it at a messy codebase and it makes a mess faster. That is why we build the architecture first.

Questions we get asked

Handing over an AI-built app

Do we need developers to keep an AI-built app running?

No. The people who know your process can describe changes in plain language, review the result and release it once the automated tests pass. For new integrations and structural changes we are available on request, and we train new team members whenever you want.

What stops AI from breaking working software?

Three things. A documented architecture the AI reads before every change, automated tests that show at once whether something broke, and a test environment where your team reviews the result before it goes live. Every change we ship is also reviewed by an architect.

Who owns the code when an outside team builds an app?

You do. The source code sits in your repository with the documentation and decision records, and there is no licence from us. If you hand the app to another team, they receive the same package, so the choice of who works on it next stays with you.

How does handover work when the app lives inside Salesforce?

The method and the handover package are the same as for any other app. The configuration and code sit in your org and your repository, your team develops with AI against a sandbox, and we come back for new integrations or structural changes if you want us to.

What does a fixed-scope blueprint cost, and how long does it take?

A matter of weeks, with fixed scope, fixed fee and a fixed end date that we agree up front. The fee depends on the process and the systems involved, and we quote it after the first call. If we build afterwards, the fee is credited against the build.

First call

Tell us what your system can't do today.

In 30 minutes we work out whether it is a case for Baucore, for Salesforce or for your own app. If it is worth doing, your blueprint is on the table on a date we fix up front.

What we need from you

  • Access to the people who run the process
  • A few real examples, such as documents, data or screenshots
  • One contact from IT for the integrations
Talk through your use case

30 minutes, free of charge. Pick a slot in the calendar and meet our team.