will you take on a small or weird project?
yes, and those are often the best ones. migrating a mailbox, rescuing a site the last agency walked away from, turning a spreadsheet into a real tool, setting up backups that were never configured. if it's technical and it's blocking you, ask. if it isn't something we should do, we'll tell you and point you at who should.
the "can you also look at…" list is where a lot of our work starts. nobody plans these jobs, they have no owner, and they sit unsolved for months because the last agency said "that's not our part". if it's technical and it's in your way, it counts.
things we've taken on
- the spreadsheet that secretly runs the business, turned into a real app with logins and history
- a site whose original builder is gone: read, documented, stabilised, and adopted
- a domain nobody could find, tracked down and moved into your own account
- backups that were never configured, set up, tested, and alerting
- two systems that refuse to talk to each other, synced both ways
- a staff member who left and still had access: revoked, then audited
- a six-step manual invoice process, automated down to one
- a client asking for a security policy you didn't have: written, reviewed, defensible
migrations belong here too: hosts, domains, mailboxes, databases, CMS platforms, moved without the weekend of downtime. so does an hour of straight vendor advice from someone who isn't paid by any of the vendors.
when the answer is no
sometimes a job is too small to be worth engaging us for, or a cheaper option would do it. we say so, and tell you how to do it yourself or who to ask. being useful on the small stuff is usually how we prove we're worth keeping around for the bigger stuff.
small budgets are fine; see is there a minimum? otherwise send it over, links included.