CRM for solopreneurs: keep follow-ups under control

Decide whether you need a CRM yet

If you finish client work at six and then spend half an hour working out whom you forgot to reply to, start with that problem. A CRM for solopreneurs should make the next action easier to find and maintain. It should earn its place in your day.

Keep your current spreadsheet and calendar if you can reliably find the latest conversation, see every action due, and distinguish a waiting client from a closed enquiry. Twenty contacts is not a threshold that requires paid software. A smaller list with frequent changes can be harder to manage than a larger, quiet one.

Consider a CRM when you repeatedly lose context between inbox and calendar, rewrite the same information in several places, or discover overdue commitments only when a client asks. First check whether a consistent routine would fix the problem. Software can surface a missing task; it cannot decide what you promised.

This guide is for one person managing a service business's enquiries, proposals, and client follow-ups. A freelancer can use the same approach. If your main requirement is preparing contracts, tracking billable work, or collecting payments, evaluate that workflow separately. The CRM guide for consultants covers more involved client relationships and separately approved engagements.

The shortlist below is based on official documents checked on September 11, 2026. We have not run these products through a week of client work. The 20-contact example and workload log are tools for your own trial, with no claimed time savings or usability scores.

Define a daily routine you can maintain

Give each active relationship a recent note, a clear next action, and a due date. Use a separate review date for a genuine pause. Keep closed enquiries out of the outreach list unless a new reason to contact them arises.

For example, Sample client 07 has an open proposal. The next action is to confirm that it arrived and invite questions on Monday. Sample client 16 is waiting for a budget decision; its review belongs after the trial week. Both records need attention eventually, but only one belongs in Monday's follow-up queue.

Open three views at the start of your working day: overdue actions, actions due today, and records waiting for a review. Complete the actual work, record its outcome, and then choose the next action. If nothing remains to do, close the task. If the client asks to wait, record the reason and revisit date rather than repeatedly postponing an unexplained reminder.

Finish the day by checking whether each still-active relationship has a next step. Keep this check small enough to repeat when you are busy. A task called "follow up" is less useful than "confirm whether the proposed start date still works."

Use the CRM requirements checklist when a capability needs a precise pass condition. For this solo routine, the central test is whether tomorrow's queue is correct after today's work changes.

Compare three CRM approaches

Keep your current spreadsheet as the baseline and select one or two products to try. The following options represent different approaches to the same daily job. They are not a ranking of the entire market.

Less Annoying CRM: keep the daily work in its task view

Less Annoying CRM tasks can have due dates and links to contacts or companies. They appear on its Calendar and on Workspace when due. That gives you a documented place to start the routine above. Task behavior.

Its automatic email logging can connect up to three accounts and save incoming and outgoing correspondence for contacts already in the CRM. It only logs messages going forward; it does not import old email history or automatically create an absent contact. Test a new reply from a saved contact and decide how you will retain earlier context. Email logging scope.

There is an important calendar distinction: its Google Calendar sync handles events, not tasks. If you work entirely from Google Calendar, establish where you will review CRM tasks before assuming the sync replaces that habit. Calendar sync limits.

Shortlist it when you want to maintain relationships and reminders inside the CRM. Reconsider the fit if your routine depends on a complete historical inbox being available automatically or every CRM task appearing in Google Calendar. These are workflow trade-offs, not claims that the product is difficult or lacks automation.

Bigin: check what the free allowance actually counts

Bigin Free has one user and 500 records per organization. Express raises the record allowance to 50,000. The free allocation is not 500 contacts plus unlimited notes and tasks. Contacts, companies, pipeline items, activities, products, and notes all consume record storage; records in the recycle bin still count. Edition limits, record storage definition.

For a deliberately simplified storage example, 20 contacts plus 20 pipeline items, 40 tasks, and 20 notes would use 100 records before any other counted data. Those are invented quantities, not the number of records our CSV creates in every CRM. Bigin's storage counter updates hourly, so an unchanged counter immediately after an edit is not evidence that the item is excluded.

IMAP email integration starts with Express; the Free edition excludes that integration. Also check the actual automation trigger. The current table gives Free three workflow/stage automation rules and Express 30, but date-field-based workflow triggers require Premier or Bigin 360. A larger rule allowance does not establish that the desired trigger is available. Email features, workflow requirements.

Try Bigin Free when its record scope and feature limits fit your routine. Evaluate Express for an integrated email account. If automatic action on a stored follow-up date is essential, investigate the documented higher-edition requirement before choosing a plan.

Pipedrive: separate the activity list from inbox automation

Pipedrive Lite includes activity/calendar management and Smart Bcc email logging. Full email sync and workflow automations start at Growth. Both plans list Projects, Smart Docs, and LeadBooster as paid add-ons. Record only the extras needed for your actual workflow. Current plan matrix.

Its current new-plan limits distinguish contacts from leads and deals: Lite allows 2,500 leads/deals per seat and Growth 5,000. Pipedrive does not impose a contact-count usage limit, although a connected contact provider can. Growth lists 50 automations and one synced email account per user. Legacy account terms should be checked separately. Usage limits.

Test Lite if an activity queue and your chosen logging process are enough. Consider Growth when the connected inbox or a specific automation removes a step you can identify. An automation is useful only if you can also maintain its exceptions, including a client reply, changed date, or requested pause.

Check the cost of one usable account

Price the configuration you would keep after the trial. Write down one editing user, the required edition, email connection, add-ons, billing period, and applicable taxes. A low headline rate can refer to an annual commitment or omit the feature that prompted the move.

Less Annoying CRM's price and 30-day trial are documented in its pricing help. Its separate storage guidance recommends staying below 50,000 combined contacts and companies for performance; that is guidance, not a hard 50,000-contact plan ceiling. Storage guidance.

Bigin's edition table separates monthly and yearly billing. Pipedrive's billing explanation states that purchased seats are charged even when unassigned and that currency depends on location. We have not collected matching local checkout quotes for all three products, so this is not a cheapest-product comparison.

Then account for your own work. Separate initial setup from routine data entry, rule maintenance, and periodic exports. Use the software cost checklist for the cash commitment and transition costs; use the log below to observe the time involved.

Prepare the 20-contact practice file

Download the 20-contact CRM practice file (CSV) and the one-week CRM workload log (CSV). Both are editable and available without an email address or account. If your spreadsheet application opens either file in one column, import it as UTF-8 with a comma delimiter.

The practice file uses Sample client 01 through Sample client 20. It has no real names, addresses, or customer correspondence. The initial distribution is:

That is 15 initial actions across five days. Three per day makes the example easy to reconcile; it is not a recommended workload or contact frequency. Real replies and new enquiries will change the queue.

Map the columns to fields your candidate actually supports. The S01-style ID identifies the sample row; it does not automatically become the product's update key. Weekday labels must become real dates in your chosen trial week. Convert each pause's review trigger to a dated internal review, not an automatic client message.

Store the relationship status separately from the task's completion state. A completed proposal follow-up does not mean that the proposal was accepted. Keep the completion evidence blank until you perform the check.

Import a small subset first, check its mapping, then load the remaining sample. Update one contact using the product's documented matching identifier and repeat that update. The contact count should stay at 20 once the full fixture is loaded. This file is a practice dataset, not a universal ready-to-import CRM schema.

Run a week that includes a missed task and a pause

Use a test account, keep outbound client messages disabled, and use only inboxes you control for email checks. The following is a proposed trial. It describes expected behavior, not results we observed.

A saved activity can satisfy the reminder test without a workflow rule. If you test automation, record which edition and trigger you used. If the proposed rule is unavailable, record that limitation and evaluate the manual route rather than upgrading just to complete the example.

After the Wednesday pause, the initial distribution is no longer the current state. S09 is now paused if you carried out that step. Keep the starting CSV as a reference and the observed log as the record of what changed. Do not force Friday's counts to match the original daily allocation.

The export check should include task and review information, not just contact names. For example, Pipedrive documents separate export routes for activities, notes, and files; a contact export alone does not establish complete history retrieval. Its trial-expiration guidance also says access becomes restricted without billing details when a trial ends. Inspect and retain the needed output before that point. Export scope, trial expiration.

Record the work the CRM adds to your week

The workload log has Setup, Monday through Friday, and Review rows. Planned tasks are filled; actual counts, minutes, observations, and changes are empty. There are no formulas or pre-filled savings estimates.

Log each minute once:

If an activity crosses categories, split the time rather than recording its full duration twice. Separate a one-time learning task from something you will repeat every week. Leave a cell empty when you did not measure it; zero should mean you measured no time in that category.

If you want to compare with your current system, record a comparable period using the same definitions and similar task types. A quieter week or fewer client replies can change the result independently of the CRM. One week can reveal friction and missing capabilities; it does not prove a permanent productivity gain.

Choose a tool you can keep using

Keep the spreadsheet if it still gives you accurate daily actions and accessible context with acceptable upkeep. Choose a CRM when the completed trial shows a useful improvement in the work you actually perform and the paid configuration fits your budget.

Before committing, make sure you can answer these questions:

• Can I find overdue and due-today work without reconstructing it from my inbox?
• Can I record a pause without losing its future review or prompting unwanted follow-up?
• Can I keep enough email context under the plan's actual logging rules?
• Can I maintain the fields and automations with the time I have?
• Can I retrieve the sample's current actions, notes, and review information outside the product?
• Does the quoted plan include the configuration I used?

Write down the unresolved issue as specifically as the successful result. "Needs a separate daily task check" is actionable. "Feels simple" is not enough to decide what you will maintain.

Start with the smallest configuration that meets those conditions. Add a field or automation when a repeated task gives it a clear purpose. Your next client commitment should remain easier to see than the settings you created to track it.