Bernot Software
Let’s look at one task together.
Thirty minutes, no cost, and no obligation to build anything. You will leave with a straight recommendation, even when that recommendation is to do nothing.
Pick a time
Video or phone, whichever you prefer. Most slots are early, late, or on a weekend, because that is when I can give you undivided attention. If you are in Flagstaff and would rather meet in person, say so when you book and I will come to you.
Booking only asks for your name and email. Prefer not to use the calendar? Just email adam@bernot.dev and we will find a time.
What to bring
- One task that happens every week and nobody enjoys
- Roughly how long it takes, and who does it
- The software you are already paying for
- A screenshot or a blank copy of the form, if there is one
What happens next
If it looks like a fit, you get a written proposal with a fixed price and a realistic start date, usually within a week. If it does not, you get the reason why and a suggestion for what to do instead. There is no follow-up sequence and no drip campaign.
Not ready to put a time in the calendar? Have a look at what I build, or the work behind it, first. The conversation is more useful when you already know whether I am the right person to be asking.
Other ways to reach me
- adam@bernot.dev
- Where
- Flagstaff, Arizona. Serving Coconino County and Northern Arizona
- Response time
- Usually within a day, from me rather than a ticketing system
- Availability
- A few projects at a time. Ask and I will tell you honestly when I could start
A few things worth knowing.
Is the consult really free?
Yes, and it is not a disguised sales call. The reason it works for me is that half an hour is enough to tell whether a project is a good fit, and finding that out early is cheaper for both of us than finding out in month two.
I’m not sure my problem is big enough.
Small problems are the best ones to start with. A narrow automation that removes one recurring chore is quick to build, easy to price, and it tells us both whether working together is any good before anyone commits to something large.
I already have a developer.
Then keep them. I am happy to look at a specific piece as a second opinion, but I am not interested in talking anyone out of a working relationship that is going fine.