Why we say no: projects we decline
Not every inquiry becomes a project. These are real reasons we've turned work down: off-platform contact requests, remote-desktop access instead of a documented setup, and work genuinely outside what we do.
Most of what a careers page says about standards is aspirational. This is not that. These are three real, recurring reasons a project gets declined here, told the way they actually happened rather than the way a values slide would summarise them. If you're deciding whether this is a team you'd want to join, this is closer to the truth than the perks list.
We decline off-platform contact requests
Every so often, a client or a prospect asks to move a conversation off the platform it started on, straight to a personal WhatsApp number or a private email, before any agreement is in place. We say no. It is not personal and it is not about trust in the individual asking. Off-platform contact outside policy means no record, no oversight, and no protection for either side if something goes wrong later. Staying on the documented channel is the boring answer, and it's the one we give every time.
We decline remote-desktop access requests
Some inbound requests come with a specific ask: install AnyDesk (or an equivalent remote-desktop tool) and let someone drive a machine directly, usually to get a platform like GoHighLevel set up faster. We turn this down and do the documented version instead — scoped credentials, a written setup, a trail that shows what changed and when. It takes longer than handing over a session. It's also the version where, six months later, anyone on either side can see exactly what happened, instead of taking someone's word for it.
If a setup can only be done by taking over someone's screen, that's a reason to slow down, not a shortcut worth taking.
We decline work outside what we actually do
Not every no is about policy. Some are about scope. We were once approached to run creator outreach for a prediction-market product — finding and coordinating influencers for a category we have no real footing in. We declined it, plainly, because doing it badly would have cost the client more than saying no up front. Turning down billable work because it isn't ours to do well is a harder discipline than it sounds, and it's one we'd rather practise in the open than pretend we don't need.
Why this belongs on a careers page
Every one of these declines cost the business money in the short term. What they buy instead is a team that isn't negotiating its standards project by project, and a working environment where nobody has to guess whether "we don't do that here" is actually true. If you've worked somewhere that said one thing about ethics and did another under deadline pressure, this is the difference we're pointing at.