惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
I
InfoQ
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 【当耐特】
小众软件
小众软件
B
Blog RSS Feed
大猫的无限游戏
大猫的无限游戏
博客园 - 三生石上(FineUI控件)
Engineering at Meta
Engineering at Meta
人人都是产品经理
人人都是产品经理
Microsoft Security Blog
Microsoft Security Blog
Last Week in AI
Last Week in AI
H
Help Net Security
爱范儿
爱范儿
云风的 BLOG
云风的 BLOG
博客园 - 司徒正美
Y
Y Combinator Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Microsoft Azure Blog
Microsoft Azure Blog
L
LangChain Blog
WordPress大学
WordPress大学
GbyAI
GbyAI
Google DeepMind News
Google DeepMind News
腾讯CDC

Danb Blog

August 2026: What I've Been Working On · Danb Blog Great Tech: Intel 2500k CPU · Danb Blog July 2026: What I've Been Working On · Danb Blog My Experience with Ubuntu Desktop 26.04 · Danb Blog Thumbnails for Orca 3MF in GNOME Files · Danb Blog Cheaper Sodastream Gas with a Big Tank · Danb Blog June 2026: What I've Been Working On · Danb Blog Running Snyk On Forgejo/Codeberg Actions · Danb Blog Tuta & Proton: An Open Source Client Does Not Result in an Open Source Service · Danb Blog May 2026: What I've Been Working On · Danb Blog 3D Printing Parts for my Greenhouse, Round 2 · Danb Blog Great Devices: Nexus 7 2013 · Danb Blog R36S Console RetroArch Stuck Menu Issue · Danb Blog April 2026: What I've Been Working On · Danb Blog Basic OpenCode Sandboxing with Docker · Danb Blog Games Played in 2025 · Danb Blog March 2026: What I've Been Working On · Danb Blog Shivam Mathur's "node-docker" Images are Awesome for PHP CI · Danb Blog February 2026: What I've Been Working On · Danb Blog Your BookStackApp project was assigned as a project for my Software Architecture course · Danb Blog My Sovol SV08 3D Printer Setup in 2026 · Danb Blog January 2026: What I've Been Working On · Danb Blog Epson Printer: The administrator password you entered was not recognized · Danb Blog Online Shopping Email Notifications · Danb Blog My HomeLab Setup in 2026 · Danb Blog Linux Label Printing with the Phomemo D30 · Danb Blog Reporting to the CMA: Google Android Developer Verification · Danb Blog OPNsense & Dnsmasq: Responding with specific DNS servers · Danb Blog An Impromptu Introduction to ZFS Drive Replacement at 1am · Danb Blog Experience with UK Medical Cannabis for Ankylosing Spondylitis · Danb Blog
Pressure to Follow Process · Danb Blog
2026-01-06 · via Danb Blog

Every so often I get an email from large businesses or organisations asking me to spend time filling a questionnaire to provide the information which they need for their procurement process. This is ultimately asking me to do their work for them, work that only exists to fit their process. Being sent from very large organisations, they probably expect businesses to jump into action and bend over backwards to win their custom. They are used to a one-sided dynamic where they have weight.

For me though, what I’m providing is entirely cost-free and open source. I’m not trying to sell it to them. I don’t want to pressure/persuade anyone to use it. In these scenarios, it’s likely they’re asking me to spend time to adapt to their process, to save them time, for a product which may save them a lot of money compared to other options.

To be clear, I’m happy to answer questions if folks have trouble finding answers about specific things, the issue I have is that there’s no apparent effort on their side to find answers before contact, despite often having an entire department or role for procurement.

I take a similar approach with my paid support services. I decline requests to sign NDA’s, to accept extra terms of sale, to fill out forms full of questions they could answer themselves. From what I’ve learnt, if a company is demanding and throwing their weight before purchasing, they will continue to do so after purchasing. IMO, life is too short to deal with that.

An Example

Here’s an example I received very recently, which prompted me to write this post, especially due to their cheeky attempt at pressure based on their own manufactured time-scales. I’d usually provide a more helpful/open response, but their lack to even fill their template properly, upon the applied pressure, led to more haste in my response.

Note: The <angle bracket> parts are those where I’ve made redactions. Their greeting was how their email was received. For context, the linked form was a 5 page Microsoft Forms links.


Dear [Recipient’s Name],

The <name of US state> government is reviewing your company’s solution, “BookStack”, for potential use within the state. As part of our vetting process, we require additional information about your solution.

Please complete the linked form within two business days or provide an estimated completion date by replying to this email. Given our six-day processing timeline, timely submission is critical to ensuring your solution is evaluated for approval.

Failure to submit the form may result in your solution not being approved for use within our environment.

We appreciate your cooperation and prompt attention to this request.

Best regards,

<Vetting department>

My Response

Hi <Sender’s Name>,

Thanks for your interest but I’m not not going to spend my time filling a form to suit your process. Especially since it’s not clear how much time it will take.

I don’t mind if this means it’s not approved for your use, I’m not trying to sell you on the solution. It’s free to use, for everyone.

Regards.
[Recipient’s Name]