How a Robsky engagement works

For first-time clients, the engagement experience with a software studio can feel opaque. This page demystifies our process and sets practical expectations.

What a discovery call actually is

The discovery call is a focused 30-minute conversation between you and Robsky about your problem. It is not a sales pitch, and it does not commit either side to anything. Its purpose is narrower:

1. To understand your business and the specific problem you are trying to solve.
2. To identify whether AI, custom software, or a simpler tool is the right answer.
3. To give you an honest estimate of likely cost, timeline, and outcome ranges — or to recommend you do not build the thing at all if it is not worth it.
4. To enable both sides to decide whether to proceed.

The conversation is confidential from the first sentence — even if you ultimately do not engage. We do not share project details outside Robsky.

What to expect procedurally

Before the call

• We will ask for a brief written summary of the problem (5–10 sentences).
• For projects involving proprietary code, customer data, or unreleased products, a mutual NDA can be signed before the call. Just ask.
• If you have an existing prototype, screenshots, or a competitor reference, share the link.

During the call

• Bring the problem, not a list of technologies. Specific tools come later.
• Plan to talk through current workflow and where it breaks.
• We will ask clarifying questions and identify the obvious failure modes early.
• You will receive a preliminary view of options, risks, and rough cost.

After the call

• If you decide to engage, a written scope is sent within 1–2 business days.
• If you decide not to engage, the conversation stays confidential.
• We can follow up with a short written summary of the call on request.

Confidentiality and NDAs

Tip

We treat every discovery call as confidential by default — NDA or not. For deeper technical conversations involving proprietary code, customer data, or unreleased products, we sign a mutual NDA before any detail is shared.

In practical terms:

• Anything you share in the discovery call is held in confidence and not used outside the conversation.
• We will never reference a client project publicly without written consent.
• Past clients are referenceable only with their explicit say-so; “logo on our site” is opt-in, not default.

How engagements are scoped

A clear written scope is the foundation of any productive engagement. The scope document spells out:

• The deliverable — described specifically (e.g., “RAG integration over 8,000 product-support PDFs, deployed on Cloudflare Workers, with cost-cap dashboard and retraining runbook”), not generally (“AI for customer service”).
• The fee structure — fixed-fee, hourly advisory, or monthly retainer. We do not change models mid-engagement.
• What is included and excluded — what the deliverable does at launch, and what would be a follow-on phase.
• Handoff — full source code, deployment scripts, and 30 days of side-by-side support are part of every engagement. No vendor lock-in.

If any part of the scope document is unclear, ask before signing. A signed scope is binding on both sides.

Common questions

Do I need to engage Robsky at the discovery call? No. The discovery call is independent of any commitment. Decide afterward.

Can I get a technical proposal without engaging Robsky? A short written summary of the call is free on request. A full architectural proposal is itself an engagement (paid hourly or fixed-fee for the deliverable) — the discovery call gives you the verbal view.

Will Robsky represent both sides of a project (e.g., us and a competitor)? We do not take projects from direct competitors of an existing client without explicit consent from both sides. We run an internal conflict check before any substantive engagement.

For project-specific questions, please contact us.