Someone technical to ask, without hiring one.

Too small for an IT department, too busy to be one. A part-time tech lead takes the technology questions off the owner's desk: what to buy, what to renew, who gets which login, and which fix to do next.

Book a free call →See a month

Small things, handled before they pile up.

A sample month for a made-up fifteen-person business. Red marks the one planned fix agreed at the monthly check-in; the rest arrives as it comes.

Week 1

MonMonthly check-inReview the register, agree this month's one fix.

WedNew hire starts ThursdayEmail, groups and two-step login ready the day before.

Thu"Is this invoice email real?"Checked by text. It wasn't.

Week 2

TueRenewal notice for a design toolThree seats paid, one used. Recommend dropping two.

FriHoliday hoursWebsite, Google listing and phone greeting changed together.

Week 3

MonA vendor's quote for scheduling softwareScored on our seven criteria, written answer by Wednesday's meeting.

ThuThis month's fixWebsite form now goes straight into the CRM.

Week 4

TueSomeone leavesAccount suspended, files kept, groups and shared logins updated.

FriRegister updatedNext month's candidate fixes listed for the check-in.

The questions owners shouldn't have to answer alone.

"Should we sign this three-year contract?"
"Who has the password for the website?"
"The new person starts Monday. What do they need?"
"A vendor says we need their AI add-on. Do we?"
"Why are our emails going to spam?"
"Is this worth building, or is there an app for it?"

A register of every tool, login and renewal.

The first thing a tech lead builds, and the thing that makes every later answer faster. Sample rows:

Tool	Registered to	Who uses it	Renews	Note
Email and files	accounts@ group	Everyone	Monthly	Two-step login enforced
Accounting	billing@ group	Owner, bookkeeper	Yearly, March	Bookkeeper has her own login
Website hosting	accounts@ group	Tech lead	Yearly, June	Domain renews separately
Design tool	Former employee	One person	Next week	Move to the group, drop two seats

A partner for decisions, not a help desk.

Illustration: a tray of written recommendations next to a help-desk bell marked not this

Not round-the-clock emergency cover
We do not sign contracts or spend money for youYou decide; we advise in writing.
Larger builds are planned separatelyso the monthly work stays about decisions and upkeep.

Built from how clients already work with us.

Illustration: a small tree grown from one question, its branches hung with tags for later projects

No client is on a formal tech lead arrangement yet, so here is what it rests on. At a dental lab, the work grew one question at a time: shipping labels, then a CRM sync, a customer-history analysis and a website rebuild. Each started as a question to us before it became a project.

Our own company runs the same way: one register, company-owned accounts, and a short list of next fixes reviewed regularly.

About working month to month.

How do we reach our tech lead?

By email, text or phone, whichever you already use. Answers to decisions come back in writing so there is a record you can find later.

Does this replace our IT support company?

Not usually. If someone already fixes laptops and printers, they keep doing that. A tech lead covers decisions, accounts, vendors and the systems the business runs on, and works alongside them.