IT and coding as a light entrepreneur: pricing, contracts and invoicing

A client needs a website, an integration between two systems or help setting up computers. You have the skills and time. The next step is to agree on what you will deliver, what it costs and how you will invoice.

Light entrepreneurship can suit independent IT assignments when you want to sell your skills without setting up your own business. Through Bisse.fi, you can invoice the agreed work and receive payment as salary. Finding the client, delivering the work and agreeing on the project remain your responsibility.

Have your first IT assignment lined up? Explore Bisse.fi’s light entrepreneurship service and check the fees so you can account for invoicing costs in your quote.

Contents

1. What IT work can a light entrepreneur do?
2. How do you find your first client?
3. Hourly rate or fixed project price?
4. What should an IT project contract cover?
5. Agree on source code, usage rights and AI
6. Data protection and maintenance in practice
7. How to invoice IT work through Bisse.fi
8. Tax cards, expenses and YEL
9. When should you consider your own business?
10. Frequently asked questions

1. What IT work can a light entrepreneur do?

A good first assignment has an outcome you can explain clearly to the client. A small website update is easier to estimate and approve than an open-ended promise to handle everything IT-related.

The assignment must also reflect independent work. Using an invoicing service does not by itself determine whether you are self-employed or an employee. The actual working conditions matter, and unclear arrangements should be resolved before agreeing to the work. Työeläke.fi’s guidance for light entrepreneurs explains the distinction.

If the work is effectively employment, or a client proposes replacing an existing employment contract with invoicing, read about when light entrepreneurship is not suitable.

2. How do you find your first client?

Turn your skills into a service the client understands how to buy. A list of programming languages says less than a concrete offer: do you build quote request forms, speed up slow websites or reduce manual data entry?

Put together a few work samples. Explain the problem solved and your contribution to each project. If a sample is a practice project, say so. Before publishing client work, agree on permission to use it as a reference and remove confidential information.

You can look for initial assignments through your network, local companies and agencies that need subcontractors. Start by discussing the client’s need. For an unclear project, offer a limited, paid discovery phase first, making the implementation easier to price afterwards.

Our guide to websites for light entrepreneurs can help you build your own service page. Explain how clients can request a quote and what information you need to prepare one.

3. Hourly rate or fixed project price?

In IT work, billable tasks can include planning, meetings, testing, documentation and deployment as well as implementation. Agree with the client on what you will bill. Your pricing must also leave room for sales work, maintaining your skills and time off.

Hourly pricing works when the scope becomes clearer as the project progresses. Provide an estimate, agree on progress reporting and obtain approval before exceeding the budget.

A fixed project price suits work whose scope and acceptance criteria can be defined in advance. Include how additional requests will be priced.

A monthly fee may suit ongoing maintenance. Define the tasks, included hours and service hours so a monthly price does not become a promise of unlimited support.

Worked example: a small website project

Suppose you estimate 20 hours for implementation, six for testing and deployment, and four for meetings and instructions. That is 30 hours altogether. The example uses €70 per hour excluding VAT. This is a calculation assumption, not a recommended rate or a claim about the industry average.

The example concerns an ordinary IT service subject to Finnish domestic VAT. The standard VAT rate is 25.5%. See the Finnish Tax Administration’s VAT rates.

If you agree on a fixed price of €2,100 excluding VAT but spend 40 hours, the amount invoiced per working hour falls to €52.50 before expenses. This is why scope and time tracking matter even with project pricing.

The client’s payment is not your salary. VAT, service fees, tax withholding and other applicable charges affect what reaches your account.

Build your quote around your own target. Use Bisse.fi’s hourly rate calculator, in Finnish, and estimate take-home pay with the salary calculator. Also see our guide to net and gross income, in Finnish.

4. What should an IT project contract cover?

The client may understand “finished” to mean a deployed service with ongoing maintenance, while you mean a version ready for testing. Describe the outcome and handover as concretely as possible.

Record at least:

1. The parties and invoicing arrangement. Who orders, who delivers, and how does Bisse.fi handle invoicing?
2. The deliverables. Which pages, features, integrations, tests and instructions are included?
3. The client’s responsibilities. When will you receive content, access credentials, materials and decisions?
4. Schedule and acceptance. Who tests the result and how is approval given?
5. Price and instalments. When will you invoice and how is extra work approved?
6. Rights and handover. What source code and documentation does the client receive?
7. Bug fixes and maintenance. What is part of delivery and what requires a separate agreement?
8. Liability and termination. What happens if there is damage, a delay or an interruption?

Adding another language version is easier to identify as extra work when the original quote describes a five-page website in Finnish. Get written approval before carrying out additions.

For a fuller framework, see agreements between light entrepreneurs and clients. Ask Bisse.fi customer support whether insurance covers your particular IT work and the responsibilities you are accepting.

5. Agree on source code, usage rights and AI

Delivering code files and granting rights to use, modify or transfer software are separate contractual questions. Agree on whether the client can have another developer continue the work and whether you can reuse general-purpose components you create in other projects.

Computer programs created in employment are subject to a specific statutory rule. Do not leave freelance rights to assumptions drawn from employment. See the Finnish Copyright Act, particularly sections 27, 28 and 40b.

Distinguish between code created for the client, components developed previously and third-party libraries. Check that open-source and paid extension licences fit the client’s intended use.

Discuss AI tools at the same time: which tools may be used and what material may be submitted to them? Treat generated code as a draft to review. Check functionality, dependencies and security before handover. For hourly work, bill actual work according to the agreed billing basis; under a fixed price, time saved through tools can improve profitability.

6. Data protection and maintenance in practice

Order information, support tickets and user accounts can contain personal data. If you process it on the client’s behalf and under their instructions, establish your role as a data processor and the need for a processing agreement. A confidentiality agreement alone does not replace the contractual terms required by data protection law. See the Finnish Data Protection Ombudsman’s guidance on processor obligations.

Agree on which systems you may access, how information is protected, and how data is returned or deleted when the project ends. Use synthetic test data whenever possible. Client code, personal data and credentials may be transferred to external tools only in accordance with the agreed terms and data protection requirements.

Define maintenance as a clear service of its own. Specify updates, backups, recovery testing and support handling. Agree on response times and availability. Promise only service hours you can actually provide.

Make costs clear too. Agree on who owns the domain and cloud accounts, and who pays for hosting, licences and usage-based APIs. Accounts and payment details owned by the client can make continuing services easier to manage if the developer changes.

7. How to invoice IT work through Bisse.fi

When using Bisse.fi’s light entrepreneurship service without your own Business ID, you agree on an assignment with the client and create the invoice through the service. Bisse.fi handles payroll and tax withholding under its terms.

Prepare:

1. The client’s correct company name, Business ID and billing address.
2. Any purchase order number, project reference and e-invoicing details.
3. A clear description of the work, work period and agreed billing instalment.
4. Actual hours and the agreed hourly rate for hourly work.
5. The correct VAT treatment and payment terms.

A useful invoice line might be “Company website implementation, agreed phase 1, 20 h × €70”. Attach the agreed time breakdown if needed. Keep approvals for additional work and acceptance of the delivery.

Receiving compensation as salary does not create your own VAT liability for that salary. This does not mean the invoicing service’s invoice to the client is VAT-free. The distinction between salary and trade income is explained in the Finnish Tax Administration’s VAT guidance for light entrepreneurs.

For a client abroad, confirm that the service supports the assignment and check the invoice’s tax treatment before accepting the quote. Start with our guide to invoicing international clients. For Finnish business clients, see e-invoicing for light entrepreneurs.

Get ready to invoice the agreed work. Register with Bisse.fi and collect the client’s billing information. If anything is unclear, customer support can help.

8. Tax cards, expenses and YEL

When payment is made as salary, provide the service with a tax card for salary income and monitor your total annual income. Include side earnings in your income estimate too. See the Finnish Tax Administration’s tax card guidance for light entrepreneurs.

IT expenses may include a computer, monitor, software and internet connection. Keep receipts and check how expenses are treated under your working arrangement. Account for costs in pricing even if the tax deduction does not work as you expected. Read more about tax deductions for light entrepreneurs.

YEL pension insurance may be compulsory even when light entrepreneurship is a side activity alongside employment, if the insurance conditions are met. Using an invoicing service does not remove this obligation. Check Työeläke.fi’s guidance and Bisse.fi’s YEL guide.

9. When should you consider your own business?

Light entrepreneurship can be a practical way to take individual assignments and test demand. Compare a sole trader business, or toiminimi, with a limited company if work becomes ongoing, purchases increase, you use subcontractors or clients require you to have your own Business ID.

Selling your own software product or an ongoing subscription service also differs from invoicing individual assignments. Consider the business structure, contracts and invoicing model together.

There is no single invoicing threshold that makes the decision for everyone. Compare service fees, administration, purchases and client requirements. Our guides to sole trading versus light entrepreneurship and setting up a limited company can help.

10. Frequently asked questions

Can a developer invoice without their own business?

Yes, independent software development and other IT assignments can be invoiced through a light entrepreneurship service. Agree on invoicing with the client and confirm that the arrangement is an independent assignment.

What hourly rate should a developer charge?

It depends on skills, complexity, responsibility and billable hours. Include planning, testing and documentation. The €70 hourly rate in this article is only a calculation example.

Is maintenance included in a website project’s price?

That depends on the contract. Define bug fixes included in delivery separately from ongoing maintenance, updates and support. Explain how services after launch will be agreed.

Can I take IT assignments alongside my regular job?

It may be possible. First check your employment contract’s rules on side work, competing activities and confidentiality. Clarify uncertainties with your employer and check whether YEL insurance applies to your side activity.

Does the client receive the source code?

Agree on this before the project. Describe which files, usage rights and instructions you hand over, and how third-party licences affect use and further development.

English version published on 21 September 2026. Based on the Finnish article published on 9 September 2026.

Is your next IT project already agreed? Get started with Bisse.fi and set up invoicing once the scope, price and terms are clear.