Thin senior bench
You can hire juniors. Finding a senior engineer, accessibility specialist, or technical search person on the Island is another story.
Agencies & development teams
Charlottetown shops, Halifax agencies, and in-house product teams across Atlantic Canada are shipping with a thin senior bench. I drop into your tools, write code your team can maintain, and stay off the client relationship.
Agency Reality
Members of the PEI Information Technology Alliance and small shops from Summerside to Halifax know this already: the talent pool is thin, the pipeline is not, and a messy freelancer can cost you the client.
You can hire juniors. Finding a senior engineer, accessibility specialist, or technical search person on the Island is another story.
Tourism launches, grant deadlines, and government projects arrive in bunches. A full-time senior hire sits idle between them.
One person, no cover, and they go quiet mid-sprint. Your project manager is left explaining the gap to the client.
One sloppy white-label handoff can damage a relationship you spent years building. You need someone who stays in the background.
Accessibility and technical search get deferred until a government, arts, or municipal client asks — and then the sprint blows up.
Overnight offshore handoffs miss Atlantic Time standups, Canadian privacy requirements, and the context of Island clients.
What I do
Front-end and back-end overflow in React, Next.js, WordPress, Ghost, and the rest of the stack your clients already run.
Staging-ready builds under your brand. You own the relationship. I stay off the call unless you want me on it.
Fixes against the Web Content Accessibility Guidelines without a redesign, so government and community clients can actually launch.
A clear punch list for ranking, performance, and crawl issues — then the pull requests to close them.
Stack decisions, migration risk, and rescue work before a bad call costs you a quarter.
I test, document, and leave notes your developers can maintain. No mystery code, no hostage retainers.
Toolkit
WordPress
React / Next.js
Cloudflare
GoDaddy
Shopify
GitLab
Webflow
Google Analytics 4
Looker Studio
Ghost CMS
BigQuery
Supabase
Bring me into the sprint as overflow capacity. I work in your repo and your tools, then hand the work back to your team.
Work
Projects where I worked inside someone else's process and left the code in good shape.
Case Study
Designing a clear, investor-facing economic snapshot for the Pictou County Partnership
Process
Non-disclosure first. Then GitLab, GitHub, Jira, or whatever you already run. No parallel process for your project manager to babysit.
We start with the ticket, the decisions already made, and who talks to the client — usually not me.
I take a clear workstream: a defined build, embedded sprint capacity, an audit, or a rescue.
Pull requests, risk notes, and standup updates in Atlantic Time. You see the work as it lands.
Documentation, access, and next steps your team can run. Nothing hidden, nothing hostage.
Resources
Practical guides and checklists you can use in the next sprint.
Explainer
A glossary is an excellent way to write technical work for a mixed audience without assuming everyone speaks the same language I do.
Field note
A website is ready to publish when users can understand what you offer, take the essential next steps, and receive what the site promises—and you have a grounded, realistic plan for handling what remains.
Playbook
Ten minutes of honest notes are enough for a useful first conversation.