- Technical specificationClauses that carry risk and cost
- Technical annex of the bidArchitecture, work plan, deliverables
- Acceptance and handoverTests, training, source code
You enter the tender,
we cover the technical side.
We are the technical partner of bidders delivering software to public institutions: reading the technical specification, the technical annexes of the bid, development as a subcontractor, acceptance testing, source code and documentation handover.
FROM FILE TO ACCEPTANCEPublic sector and tenders
You are the bidder; we carry the technical load with you.
WHO IT IS FORThe technical side
The technical side
of the bid file.
- BiddersYou are the company with the administrative qualifications and the track record; the build needs a technical team.
- Joint ventures and consortiaYou are bidding as a partnership and need the party that takes on the software line item.
- Public sector contractorsA new software item came up under a framework agreement or an ongoing contract.
- In-house project teamsYou want to discuss what is technically reasonable to ask for before the specification is written.
WHAT WE DOFrom the file
From the file
to acceptance.
Technical specification review
What each clause means technically, which items carry risk and cost, which wording is ambiguous — a written review before the bid.
Technical annexes of the bid
Support in preparing the solution architecture, work plan, team structure and delivery items.
Subcontracted development
The contract sits between you and the institution; we build the software item as your subcontractor.
Acceptance and handover
Technical support through inspection and acceptance, test records, training, source code and documentation handover.
PROCESSFrom before the bid
From before the bid
to the warranty period.
- 01
Pre-bid review
The specification and any existing system are reviewed; technical scope, dependencies and risks are written out.
- 02
Technical bid support
Content for the technical section of the bid file, with the promise matched to what is actually deliverable.
- 03
Development
Scope items are delivered in order; progress is reported in a form you can present to the institution.
- 04
Acceptance, training and handover
Acceptance tests, user training, source code and technical documentation; the warranty period runs per the contract.
LET’S BE CLEARWhat we do
What we do
and do not do.
- You are the bidderCM apps Software LLC is a US company. We do not promise to appear as a bidder in tenders in Türkiye; we work as a technical partner or subcontractor. The contracting and invoicing setup is settled in the first conversation.
- No claims about certificatesTrack-record certificates, qualification and guarantees are the administrative side and belong to you. We make no promises there.
- Source code can transfer to the institutionIf the specification requires the source code to be handed over, we work accordingly; which components transfer is written down up front.
- Where data lives is written downData residency, backups and access logs are part of the technical scope — not a conversation for later.
IN THE FIRST CALLLet’s read the
Let’s read the
specification together.
Seeing the technical weight of a specification before the bid prevents the surprises that show up after winning it.
- 01
Which delivery items and acceptance criteria does the specification list?
- 02
Is integration with the institution’s existing systems required?
- 03
How are source code, data and documentation handover defined?
- 04
What does the warranty and maintenance period cover?
QUESTIONS ON YOUR MIND
Before we start.
Can you bid on our behalf?+
No. You are the bidder; we work as a technical partner or subcontractor. As a US-based company we make no promises about bidder status.
Do we have to write the technical specification?+
When we work on the bidder side we review the specification and report the clauses that create risk or cost. Specifications written by the institution are a separate process and we are not a party to it.
Is the source code handed to the institution?+
If the specification requires it, yes. Which components transfer, the open-source licences and the status of any prebuilt components of ours are written into the contract.
Is data kept in-country?+
If required, yes; hosting is planned accordingly. It is a technical scope item and it affects cost, so it is discussed up front.
Do you take part in the acceptance process?+
Yes. Acceptance tests, test records and training are part of the technical scope; we answer the institution’s technical questions alongside you.
NEXT STEPTell us about your business.
Let’s talk about your project