Looking forward to meeting you.

Our first call is a 30-minute conversation about what you want your team to be able to do, and whether 2690 can help.

If you just booked, check your calendar invitation for the confirmed time, time zone, and meeting link. This page is your guide to the conversation.

One example is enough.

You do not need a technical brief or a presentation. A recent task, a spreadsheet, or an idea you can explain is a useful starting point.

What happens today?

Pick one job. Tell us who does it, which tools they use, and what takes more effort than it should. If this is a new capability, explain what you want the team to be able to do.

What would better look like?

A faster approval, fewer manual updates, a report you can trust, or a tool your team would use every day. Share numbers if you have them. Estimates are fine when you label them.

What should we know?

Mention a deadline, budget range, or system that has to stay. Bring the person closest to the work if it helps. You can also come on your own.

What we will talk through.

We will ask questions about the work before recommending software.

The job and the people

We will understand what happens now, who uses the result, and where you want things to improve.

A sensible starting point

We will discuss whether the next step is connecting tools, building an internal application, reviewing a prototype, or making better use of software you already have.

Fit and next steps

If there is a fit, we will agree what we need to review before proposing a scope, price, and schedule. The first call does not commit you to a project.

Before we talk.

Answers to the practical questions.

Is the first call free?

Yes. It is an introductory conversation to understand the opportunity and decide whether working together makes sense.

What do projects cost?

The 2690 Build starts at $10,000. Scope and complexity determine the proposal. We also offer a Prototype-to-Production Readiness Sprint from $7,500 and a Company Brain / HQ Install from $5,000.

How long does a build take?

Small sprints start at three weeks. Larger builds are usually planned for five to six weeks, or delivered in phases. We agree the schedule after reviewing scope, access, and feedback dates.

Do we need an AI project in mind?

No. Bring the work you want to improve or a capability you want to add. AI is one option when it has a useful role.

Should we send anything beforehand?

It is optional. A short note or Loom showing the job helps. Remove customer information, passwords, and other sensitive details from examples. Email matt@2690.ai if you want to share context.

Will you need access to our systems?

You do not need to grant access for the first call. If a next step needs system access, we will agree what is needed and how to provide it.

Do we have to use HQ?

No. We build around the tools and working environment that fit your team. A normal browser-based application or client portal can be part of the project.

How do I reschedule?

Use the reschedule or cancel link in your booking confirmation. If you cannot find it, email Matt. The calendar invitation is the source for your meeting details.

Want to show us the job?

Reply to your confirmation email or send Matt a few sentences and a Loom link. It is optional; we can talk it through on the call.

Send Matt an example

Explore the product operations demo. It uses fictional data.

Still choosing a time? Book a call.

May we use Google Analytics to understand visits and improve this site? Analytics cookies are optional. Privacy details