Skip to main content

Tell us what you are trying to build

A few sentences is enough. You do not need a specification, a budget approved, or a clear idea of what the software should be — working that out is part of the job.

We read every message ourselves. You will get a reply within one business day with either a straight answer, a question, or a time to talk.

Only if you would rather be called than emailed.

What is the problem today, who it affects, and what it would look like if it were solved. Anything else you tell us is a bonus.

We use what you send here to reply to you, and for nothing else. No mailing list, no sharing it with anyone. Privacy

Prefer to email?

Email: info@dnscomputingsolutions.com

Reno, NV

What to bring to the first call

Nothing formal. But the call goes further if you have thought about these:

  • What happens today. The current process, including the spreadsheet or the notebook or the person who just knows.
  • Who touches it. Staff, customers, you — and what each of them should and should not be able to see.
  • What it costs you now. Hours a week, mistakes a month, work you turn down. This is usually the number that decides whether the project is worth doing.
  • When it needs to exist. A real date, if you have one. A season counts.

If a fixed budget already exists, say so on the call. It saves both of us designing something you were never going to buy.

What happens next

  1. We reply within one business day. A person, not an autoresponder.
  2. A half-hour call. You describe the problem. We ask questions. No slides, no pitch.
  3. A written scope, with a price and a date. Usually within a few days of the call. If the project is too large or too unclear to price honestly, we will say so and propose a paid discovery sprint rather than guess — details on the services page.
  4. You decide. The scope is yours either way. There is no pressure and no follow-up sequence.