MILabs
Tools

Devin Desktop setup for small business software

Devin Desktop, the AI coding app formerly called Windsurf, and how MILabs sets it up for small business software projects.

Updated 2026-08-22

What Devin Desktop (formerly Windsurf) is

Devin Desktop is a desktop application for AI-assisted software development, made by Cognition and previously called Windsurf. A developer installs it on a computer and works on code inside it, with AI help for writing, reading and changing the software being built. The tool works inside the development workflow, so the people who notice its results are usually the staff who use the finished software. It can help a developer build or change an internal system, a website feature or an integration more quickly than working by hand. A developer reads each change, runs the tests and decides what goes live, which keeps the business in charge of its software. Owners who see the tool this way tend to get the most from it. They treat it as a capable assistant for a developer, and they keep decisions about scope, data and release with the people responsible. This page explains how MILabs uses the tool when a business has software to build or maintain.

Cognition: official site

Devin Desktop (formerly Windsurf) in plain language

Software that an AI coding assistant helps write is a different kind of tool from a chatbot. A developer works with it in an editor, asking for code, reading suggestions, and making changes across a project's files. The assistant can read surrounding code, propose edits, and explain what a block of code does, which lets a developer cover ground that once took much longer by hand. Tools in this group sit alongside other coding aids such as command-line agents, browser-based builders and editor extensions, and they differ mostly in how they connect to a project and where the code is stored. For a small business, the subject matters because most custom software begins with a person who can read and judge code. The assistant speeds up the mechanical work of writing, testing and tidying software, while design, data handling and release decisions stay with the people responsible. Understanding this split helps an owner ask sensible questions before any work begins.

What businesses use it for

  • Adding a feature to the company website or online ordering page
  • Writing a small internal app that replaces a shared spreadsheet
  • Connecting two existing systems, such as a booking tool and a customer list
  • Updating and tidying code that a previous developer left behind
  • Drafting tests and documentation for software the business already relies on
  • Prototyping a customer-facing portal before deciding whether to build it fully

Who it suits

  • Software teams that already use Git for version control
  • Owners with an in-house developer who wants AI help in the editor
  • Businesses with one or two custom internal tools to build or change

How MILabs sets it up

MILabs starts a Devin Desktop setup with the owner, choosing the plan that matches how many people will use the tool and what they will use it for. Next, the team connects Devin Desktop to the systems the business already runs, such as its code repository, hosting account and project tracker, so work happens where the code already lives. Permissions come next. Each developer receives access only to the projects they need, and sensitive credentials sit in a secure store rather than shared files. Finally, the owner and MILabs agree who looks after the tool day to day, who approves updates and who reviews code before it reaches customers. The scope follows the team's size and the software in use.

Builds it fits

Industries it fits

Devin Desktop (formerly Windsurf) in practice

In a business that uses an AI coding assistant, the work usually begins with one developer and one piece of software. Someone on the team, often the person who already maintains the company's spreadsheets or website, describes a change in plain terms. The developer opens the project, asks the assistant to draft the change, and reads each proposed edit line by line before accepting it. Much of the day then goes on checking. Tests are run, the change is compared with existing behaviour, and unfamiliar code is traced back to the rest of the project. The change then moves through the business's usual review, where a second person reads it and agrees it should go live. Documentation is often updated in the same pass, since the assistant can draft a short explanation of a function and the developer corrects it where needed. Over time the team builds a habit of giving precise instructions, which tends to produce code that needs less rework. Most of the value sits in that loop of asking, reading, testing and deciding.

good questions, straight answers

Frequently asked questions

Can my team use Devin Desktop without training?
Yes, developers who already work in a code editor will find Devin Desktop familiar. The team still learns how it handles their own projects, and during setup MILabs walks through the parts the team will use day to day and records the agreed working practices in a short written note. Teams new to AI coding tools build confidence by comparing suggested changes with their existing code.
Can MILabs build on top of Devin Desktop?
Yes. MILabs can use Devin Desktop while building a custom app, portal or integration for a business. The tool helps the developer write and change code. Design, testing and release stay with MILabs and the business owner, who agree the scope in writing. Where a job needs other software, the build uses whatever suits it. The easiest first step is to say hello through the enquiry form, and we'll take it from there.
What does a Devin Desktop setup need from me?
A setup needs an owner who can make decisions about the business's software and approve access for the team. It also needs the code repositories, hosting accounts and project tracker the tool will connect to. The business names one person who looks after the tool, approves updates and reviews code before release. Scope is agreed in writing before any work starts.
What does Devin Desktop not do?
Devin Desktop works on code inside a developer's environment. It does not decide what a business should build, and it learns the business's priorities only when someone explains them. It does not answer phones, keep books or hold a customer database. Any link to those systems is built deliberately. A person reviews the changes and decides what goes live.
Is Devin Desktop suitable for a small business?
Yes, provided the business has someone who can read and review code. A small business with an in-house developer, or one that works with an outside developer, can use Devin Desktop to move faster on a specific project. A business with no technical staff can have MILabs supervise the work during a build. The right fit depends on the project and on who reviews it.
let's make something happen

Workflow automation: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.