Working with Falcra

Founder

Drew Salem founded Falcra and created Instant. He is a digital transformation consultant and former CIO, with more than 30 years across energy, manufacturing, logistics and ecommerce.

Drew has led technology at executive level and delivered it hands-on, and he brings both to every engagement: the governance a CIO expects, and the delivery that puts working software in front of the business in days.

Most organisations haven't heard of it

Most companies know AI-assisted development: developers using AI to write code faster. Few know the AI-Driven Development Lifecycle (AI-DLC) exists, or what it can do: an AI driving the whole lifecycle, from requirements to tested software, in days. It has already been used to save millions of dollars in software licence fees. That is a problem for any organisation that would benefit from it, because you can't adopt what you haven't seen.

Falcra brings AI-DLC to you, run the Instant way, so it is streamlined from the first day and avoids the pitfalls of an AI building at speed.

Falcra's job is to bring it to you. We build a real application with you, in your own organisation, using your own people. Then we show those people how to do it themselves. It is the old idea of teaching someone to fish, rather than handing them a fish: you end up with working software, and with the capability to keep building this way.

Why this is lower risk for you

Adopting a new way of working is a risk. A course or a tool leaves you to find out for yourself whether it works in your organisation. With Instant, you see it work first, on a real application of yours, with your own people in the room. You decide whether to adopt it after you have seen the result, not before.

What "teach" means in practice

Your people are in the room for every stage. They watch the AI build, answer its questions, make the decisions and sign the evidence. By the end of an engagement they have done the work themselves, with us beside them. That is how the capability stays with you when we leave.

What you end up with is the application and the capability to keep building this way.

What Falcra commits on your data

We want you to have peace of mind about where your data goes and what happens to it before our first meeting.

Our preference: your machines, your environment

Wherever possible, the build runs on equipment and environments you provide and control: your laptops, your code repositories, your development, test and production environments, and your AI account. Your data then never leaves your own systems.

When we use our own equipment

If you can't provide equipment, we build on Falcra's dedicated work machine, under these commitments.

1. Separate from everything else. Client work happens only in a dedicated work account, never a personal one.
2. Encrypted. The whole disk is encrypted. Your project lives in its own encrypted container, with its own password, separate from every other client.
3. Never mixed with other clients. Each client has separate code identities, access keys, containers and password vault.
4. Your AI account, where possible. The AI runs through your own AI account, for example Claude through your Amazon Bedrock. Processing stays in Australia where the model is available there. If it isn't, or if your own account can't be used, we agree the alternative with you in writing before the Blitz.
5. No personal cloud. Your data is never stored in personal cloud services, and only in backups your contract allows.
6. Recordings and transcripts of every session are made with everyone's agreement, obtained during preparation, and handled under your policies.
7. Returned and deleted at the end. Everything you own is handed over in the agreed form. Our copies of your data are deleted, and you receive written confirmation of what was returned, what was deleted, and when. Falcra keeps its own business records, such as the contract, invoices, tax records and evidence of the work needed for the warranty and insurance, with none of your data in them. If Falcra's own AI account was used, the AI provider may hold prompts for a short period under its own terms. This is outside Falcra's control, and using your own AI account avoids it.
8. Breach notification. If we suspect your data has been lost, accessed or disclosed without authority, we tell you within the time set in your contract, typically 24 to 72 hours, and help you respond.

Your rules win

Your security, privacy and data-handling policies apply. Where they are stricter than ours, we follow yours. If you ask for it, your security lead's constraints package sets hard limits that the build cannot break (Practices, chapter 1). We agree the data-handling approach with you during preparation, before any data is shared.

What we ask you to confirm during preparation

• Whether you will provide machines and environments, or use ours.
• Which AI account the build will run on, and whether processing must stay in Australia.
• Any rules on where your data may be stored, and for how long.
• Who signs the end-of-engagement return and deletion confirmation.