PROJECT023 logoPROJECT023
Novi Sad / Serbia
08 / CONTACT DIRECT / CONFIDENTIAL

START THECONVERSATION.

Tell us the problem, the outcome you want and what makes the situation difficult. You do not need to send proprietary details in the first message.

AI / SOFTWARE / DATA / R&D
NOVI SAD / SERBIA
PRIVATE BY DEFAULT

01 / DIRECT

ONE
CLEAR
CHANNEL.

For a new project, a difficult system, an experimental AI problem or a confidential engagement, contact Project023 directly.

No sales maze. No forced form. Start with enough context to decide whether a useful conversation exists.

EMAIL / PRIMARYinfo@project023.comOPEN EMAIL ↗EXTERNAL / LINKEDINPROJECT023
DJVDOPEN LINKEDIN ↗
BASE / COMPANYNOVI SAD
SERBIAPROJECT023 DJVD DOO

02 / FIRST MESSAGE

MAKE THE
PROBLEM
VISIBLE.

A useful first message does not need a 40-page specification. Four signals are enough to begin.

01 / PROBLEM

What is difficult today?

Describe the workflow, system or decision that creates friction, risk or lost leverage.

02 / OUTCOME

What should become possible?

Explain the result you want rather than prescribing technology before the problem is understood.

03 / CONSTRAINTS

What cannot be ignored?

Security, privacy, legacy systems, timing, regulation, human review or other hard boundaries.

04 / CONTEXT

Where does it have to work?

Share only the non-sensitive context needed to understand the environment and operating reality.

03 / CONFIDENTIALITY

PRIVATE
BEFORE
DETAIL.

If the discussion requires an NDA, say so in the first message. We can start at a non-sensitive level and agree the confidentiality boundary before proprietary information is exchanged.

Client identities, internal data and proprietary implementations remain private when protected by confidentiality agreements.

NDA / PRIVATE ENGAGEMENTSYOU DO NOT NEED TO DISCLOSE SENSITIVE INFORMATION TO START.

04 / RESPONSE PATH

FROM
MESSAGE
TO SCOPE.

A short path designed to find fit quickly and protect confidential information before deeper technical work begins.

01 / BRIEF

Send the problem.

Start with the non-sensitive context, desired outcome and hard constraints.

02 / FIT

Check relevance.

Determine whether Project023 is a strong fit for the system, research question or engagement.

03 / BOUNDARY

Set confidentiality.

Agree what can be discussed and whether NDA protection is required before proprietary detail.

04 / SCOPE

Define the next move.

Shape the technical path, validation steps and practical engagement around the real problem.

05 / START

READY
WHEN
YOU ARE.

Send the first message directly to Project023. Keep it concise. The problem matters more than the pitch deck.

info@project023.com ↗LinkedIn ↗