Author

Mark McNeece

Director of BSolve IT Limited. He writes everything published on this site, and he is also the person who did most of the work it describes.

The person

Who he is

Mark McNeece is the director of BSolve IT Limited, company 04607330, incorporated in England and Wales on 3 December 2002. He runs the five brands the company operates: 365i, Press Forge, 365i Web Design, McNeece Web Design and AI Visibility.

He works from Kettering in Northamptonshire. The company has never been sold, never taken outside investment, and has traded continuously under the same registration for more than two decades.

The route

How he got here

Listed as dates rather than summarised as experience, because "over twenty years in the industry" is not a checkable claim and a list of years is. The same ten entries appear on every profile page the group publishes, and they carry the same years on each one.

Mid-1990s
Boots Board BBS & ISP. Built and operated a bulletin board that grew into a worldwide community of thousands of users, then into a full internet service provider with banks of modems, leased lines and a dedicated Class C IP block. Sold in 1997.
Late 1990s
Enterprise consulting. Enterprise-level projects with Microsoft partners including QA Consulting and Anite Systems.
Founded BSolve IT Limited. Incorporated in England and Wales on 3 December 2002, company 04607330. The date on the company history is the one on the public register, for the reason given there.
Launched 365i Hosting. Managed hosting under that entity: WordPress hosting, web hosting, VPS and managed cloud servers. Same year as incorporation, and 365i has stated 2002 on its own about page throughout.
AI Visibility Definition. Published the AI Visibility Definition and the 10-file AI Discovery Files Specification, with the checker and the quarterly adoption research that followed.
365i Web Design. A design brand separated from the hosting business once it had a distinct customer base, which is how every brand here was split off.
Press Forge. WordPress builds and specialist services, split out on the same principle.
Published author. Articles at The Financial Executives Journal on AI strategy and technology for business leaders.
AI Discovery Files plugin. A WordPress plugin generating all ten machine-readable files from the dashboard, published on wordpress.org.
Mailbox MCP. A remote MCP server giving Claude, Cursor and any other MCP client real read and write access to a mailbox the user already owns, on Gmail, Microsoft 365 or any IMAP host. Published by BSolve IT Limited. The panel further down this page has the detail.

The gap between 2002 and 2025 is not a gap in the work, it is a gap in the things worth putting a year against. Those twenty-three years were hosting and building for other people, and that is counted on the work page rather than dated here.

The job

What the job actually involves

The honest description of the role is that it is four jobs that happen to share a desk.

  • Support. He answers hosting tickets himself, including the ones that arrive at eleven at night. The group publishes its ticket timings rather than describing them, which is uncomfortable and also the point.
  • Building. Hand-coded PHP sites, WordPress builds, migrations and the performance work that follows. Most of the sites shown on this site were built by him.
  • Measuring. The counts, the dispositions, the PageSpeed runs and the Search Console reading that turn a project into something publishable.
  • Writing. This site, and a substantial share of what the five brands publish.

There is no editorial team behind this site. On a single-person site the author and the reviewer are the same person, and this site declares that on every page rather than inventing a second name to make the byline look more institutional.

The output

What he writes here

Everything on this site. The sites below are the current showreel rather than the record: eight builds chosen because you can open every one of them right now and check what is claimed about it.

Eight is what is on show, not what there is. The platform he runs holds 244 live hosting packages across 414 domain names, counted from the hosting platform's own API on . Some of those he built, some arrived already built and he keeps them running, and a good number of the sites he did build have since been rebuilt or retired by the people who own them. Twenty-three years of web work does not sit still long enough to be listed. A portfolio can only show what is still standing.

Not all of it is websites. The newest thing here is software: Mailbox MCP, a remote MCP server sold by BSolve IT Limited rather than through any of the brands above. It is not in the showreel because the showreel is sites you can open and check, and that is a different kind of thing. What it does, and what was measured.

Most of the writing is on the brand sites rather than here: 325 articles across the four that publish, counted from each site's own post sitemap on . The 365i news desk carries 120 of them, the McNeece blog 109, the 365i Web Design news desk 80 and the Press Forge blog 16. Where a piece there covers the same ground as one here, the brand piece is the one that goes into detail on a single client, and this site publishes the pattern across several.

The product

What he has built that is not a website

One thing here is neither a client project nor a hosting account. It is a product, it is sold, and it is the newest thing on this page.

Mailbox MCP

Mailbox MCP is a remote MCP server. You connect a mailbox you already own, on Gmail, Microsoft 365 or any IMAP host, and Claude, Cursor or any other MCP client can then use it: read, search, draft, send, reply inside the right thread, file mail away, and check whether what you sent arrived and was opened. Nothing is migrated and no message content is stored.

The rule it is built to is that the mail client is the oracle. If you open Outlook afterwards and can tell a machine did the work, the feature is not finished, whatever the tests say. So the rows below are about what the mailbox looks like afterwards rather than about what the server returned.

Verified behaviour Live mailbox, 26,930 messages
  • Replies thread properly In-Reply-To + References
  • Attachments arrive intact SHA-256 identical
  • Sent mail is filed once 1 copy, ID matched
  • Reading leaves it unread flags untouched
  • Duplicate copies in Sent 0

Free tier, 5 calls a day. Pro is £34.99 + VAT per mailbox, per year. It launched in August 2026 and the rows above were taken from one live mailbox of 26,930 messages. That is a measurement, not a study.

The Mailbox MCP robot, holding up a letter with a stack of post under its arm

The limits

Where the expertise comes from, and where it stops

The expertise on this site is practitioner expertise, not academic expertise. It comes from having built, hosted, broken and repaired a lot of small business websites over a long period, and from measuring what happened afterwards. Where a figure is published here, he took the measurement or watched it being taken.

The limits are worth stating as plainly as the credentials, because an author page that only lists strengths is a marketing page.

  • He is a practitioner, not a researcher. The samples on this site are single figures, not studies, and the pages say so.
  • He does not do paid search, social media or brand strategy, and does not write about them.
  • He has no access to Google's internal ranking behaviour, and neither does anyone else outside Google. Where this site describes what Google does, it quotes Google's own documentation and links to it, rather than describing the algorithm from the outside.
  • Several projects cited here are weeks old. Where the outcome data does not exist yet, the pages say it does not exist rather than substituting something directional.

Corrections

Corrections and contact

If something published here is wrong, the fastest fix is to say so. Corrections go to support@bsolveit.com, are investigated within seven days, and any needed correction is published within fourteen days of being confirmed. Substantive corrections are recorded in the affected page's update log rather than edited in quietly.

The full process is on the editorial standards page, and how figures are sourced in the first place is on the build standard.