Skip to content
Phi-Lean.ai – True Lean software automation

Building engineering firm

Public tenders spotted every morning, and the go/no-go decision made in ten minutes

Public contracts are a large share of revenue, but tender watching happens at the end of the day, and some files are found too late. Phi-Core reads the notices every morning, discards what does not concern you and prepares a decision sheet for the rest.

Target

10 min

to decide whether to bid

The scenario

A 25-person building services engineering firm bidding for local-authority contracts in three counties.

The flow, end to end

This use case, laid out on the Phi-Core architecture.

  1. What triggers it

    • Schedule & web watchEvery morning at 7 a.m.: new public tender notices

  2. The agents at work

    Phi-Core
    • Company UnderstandingGathers what is known about an organisation: its business, its public data, its history with you.
    • SynthesisCondenses onto one page what matters for the decision.
    • DraftingWrites replies, quotes and reminders, in your tone and your house style.

  3. You validate

    The managing director decides go or no-go; nothing is submitted without him.

  4. What comes out

    • Briefs & synthesesOne-page decision sheet for each relevant notice
    • Tasks & approvalsBid file opened, with the list of documents and deadlines
    • Drafts ready to sendTechnical proposal outline drawn from your past bids

Today

  • Tender watching is done by hand, across several platforms, when there is time.
  • Relevant notices are found a week before the deadline.
  • The decision to bid is made without written criteria.
  • Every technical proposal starts from scratch.

With Phi-Core

  1. Every morning, Phi-Core reads the newly published notices in the French and EU official journals (BOAMP, TED), by your discipline codes and areas.
  2. The understanding agent reads the notice and the buyer: subject, estimated value, criteria, deadlines, required references.
  3. It scores the notice against your criteria and discards the rest.
  4. For each notice kept, the synthesis agent writes a one-page sheet: interest, risks, documents, deadline.
  5. The managing director decides in ten minutes; if it is a go, the file opens with the list of documents and a proposal outline drawn from your past bids.

What we look at first

Before plugging anything in, we spend time with the people who do this work. That is where most of the value lies: a well-understood flow automates simply; a poorly understood one automates badly, whatever the tool.

  • Your real go criteria: disciplines, values, areas, required references, current workload.
  • Your won and lost bids, to see what works.
  • The administrative documents to keep up to date at all times.

What changes

  • No relevant notice found too late.
  • Bid decisions made on criteria.
  • Technical proposals that build on earlier ones.
  • More time for the bids you can win.

Plugged into your tools

Open public procurement data, the shared storage of your past bids, e-mail, the task tool.

Safeguards

  • Submitting a bid remains a human decision and a human act.
  • Technical and financial commitments are written by you; Phi-Core prepares the outline.
The Lean principle behind this caseThe result: Profitable today and tomorrowMaking money, now and in the futureRead on phi-lean.com

Does your flow look like this one?

Describe it in a few lines: we will tell you where we would start, and what we would look at first.

Talk about my flow

Typical scenario, built to illustrate Phi-Core; it is not a client reference. The targets shown are design goals: yours are set during the diagnostic, from your real flow.

Other use cases

All use cases

Which of your flows deserves to be automated?

Thirty minutes is often enough to spot the flow that will pay back most, and what needs fixing before any AI is plugged in. No commitment.

Book a callAsk for a diagnostic