Adam Menczykowski
Technical Director
Hi, I’m Adam — Technical Director and Co-Founder here at You I.
If you’ve worked with us, you already know that we’re a small team with big ambitions — and that means my role isn’t just “technical.” It’s part developer, part designer, part strategist, part problem-solver - a wearer of many hats.
People sometimes ask what a typical day looks like for me, so I thought I’d share a behind-the-scenes look.
8:30am – Starting with Intention
Mornings begin with a quiet moment before the code. I check my handwritten diary from the night before to see broad strokes of my day ahead.
I check Laravel Nightwatch and Sentry across client sites to see how things are performing. Any traffic spikes? Conversion dips? Broken form submissions? Server errors? Hopefully not.
We take stability & performance seriously: not just at launch, but every day after. If something’s off, I flag it early so we can fix it fast.
9:00am – Dev Deep Dive
My mornings are usually blocked out for deep work — coding new features, building out backend functionality, implementing front end components, or refining infrastructure.
Today’s project: a custom member portal built on Laravel and Statamic, with a slick UI powered by Vue.js.
This is where I thrive — in the weeds of problem-solving, writing clean code, and building something from the ground up that just works (and works beautifully).
11:30am – Client Check-Ins
Time for a couple of calls. At You I, we work closely with clients — whether it’s a weekly project check-in or a quick idea-sharing session on Trello.
This morning, I’m chatting with a client about:
How we’ll roll out a new feature where member signup falloffs can be tracked.
How to streamline their blog content workflow by auto publishing to a Transpond email automation.
What’s possible in the next fortnight’s hours for them.
I love these calls. They’re not just about deliverables — they’re where partnerships are built. This collaboration and creative idea space is one of my personal favourites.
1:00pm – Quick Break
Cooked Lunch. Feed my home made Kefir, batch cook a salad for the rest of the week perhaps.
2:00pm – Support & Iteration
Afternoons are often reserved for ongoing support work.
This might mean:
Deploying new features for long-term clients
Performance tuning (site speed still matters, always)
Responding to client requests via Trello
Because we offer ongoing support packages, most of our client relationships last years — not weeks.
We know the sites, the people, and the goals, so when they ask for something new, we already understand the bigger picture.
4:00pm – R&D, Planning, or Quiet Focus
Depending on the day, this is when I:
Explore new tools, frameworks, or performance techniques
Sketch out UX flows for an upcoming feature
Plan dev roadmaps for upcoming launches
Revisit our own website to improve a page or test an idea
Because while client work comes first, we’re always investing back into our own processes and learning.
6:00pm – Wrapping Up
I finish the day with a quick review of:
What shipped
What’s left
What needs adjusting tomorrow
All handwritten in my journal. I find writing this down helps me to be able to leave work at work.
I didn’t start You I to build websites. I started it to build solutions that help people move forward — and to do it in a way that feels personal, honest, and grounded.
Every day is different. Some are heavy on code. Some are all strategy. Some are chaos (in a good way). But all of them are about the same thing: helping good businesses grow through great digital experiences.
Want to chat about your next big idea?
I’d love to hear it
We build bespoke web platforms and custom business software that automate processes, improve efficiency, and scale with your organisation — powering lasting digital growth.
Adam Menczykowski
Technical Director
