Yes. It is a choice: one person accountable for the product, the architecture and the code, with no coordination layer. For brand design or content, I work with identified partners, named in the proposal.

What happens if the project runs late?

If the delay is on my side, the price does not move. If it comes from a dependency on your side (access, content, decisions), the calendar shifts accordingly and the price stays the same.

Yes, on request, before any sensitive information or code access is shared.

NILSON

← Home Start a project

How it works

How an engagement runs, from the first question to production.

One accountable builder from start to finish, a written scope, a fixed fee, a demo every week and a product in production at the end — with the code, the accounts and the documentation in your name. Here is every step, what you provide, what happens when scope changes, and where support stops.

Updated 24 Sept 2026

01 — Steps

Eleven steps, in this order

Discovery: You describe the project: six questions and the context. Personal reply within 24 business hours, with an honest orientation — build, diagnose first, or something else.
Diagnostic: When the scope, budget or complexity is not settled: the product and architecture diagnostic, CHF 2’400, seven working days, 100% credited against the build.
Scope: A written proposal: problem, objective, scope, exclusions, architecture, milestones, acceptance criteria, what I need from you, price and payment schedule. Within 48h of the call or the diagnostic.
Contract: The signed proposal is the contract, together with the terms: code ownership, confidentiality, change control, warranty.
Initial payment: Usually 40% on signature. The build starts the following week.
Build: On the production environment from week one — no “we will deploy at the end”. Data model first, business logic tested outside the interface, then the screens.
Weekly demo: Every Friday, the product as it is, in production. You approve or correct the course — never a surprise at the end.
Acceptance: Against the criteria written in the proposal, not against an impression. What is accepted is accepted; what is not gets fixed before go-live.
Production: Domain, live payments, email, backups, error alerts. The product is live on your accounts.
Handover: Repository, access, architecture and operations documentation, a handover call. Your team or another engineer can take over without me.
Continuation: Only when it makes economic sense: a fixed monthly capacity to keep improving the product. No ticket-based maintenance, no default subscription.

02 — Terms of work

What is agreed before starting

Communication: One written channel (email or shared Slack), a demo on Fridays, a reply within 24 business hours. No status meetings: the demo is the status.
What you provide: A decision-making contact available for the demo; access (domain, Stripe, email) within five working days; content and business rules before the week they are built. A delay on your side shifts the calendar, not the price.
Scope changes: Any new request is priced in writing before it is built: it replaces an item of equivalent value, or it becomes an amendment to the fixed fee. Never retroactive hourly billing.
Deployment and accounts: Everything is created in your name from the start: hosting, database, Stripe, email, domain. I work with delegated access, which you revoke at handover.
Credentials and secrets: Never by email or in the code. Secrets live in your accounts’ environment variables; a shared password manager for the rest.
Support boundary: Thirty days of warranty after acceptance: any deviation from the acceptance criteria is fixed at no cost. New features, third-party provider changes and day-to-day operations are outside the warranty.

03 — Guarantees

Process guarantees, not promises

No honest builder guarantees a product’s commercial success. What can be guaranteed is how the work is done — and each of these points can be checked.

A written scope and signed acceptance criteria before the first line of code.
A production demo every week — you see real progress, not a report.
No surprise hourly billing: the fixed fee only moves through a written amendment you accept.
Go-live on your accounts, with handover and documentation.
Source-code ownership transferred on full payment.
Thirty days of free fixes for any deviation from the acceptance criteria.

04 — Comparison

Internal hire, agency, freelancers or one accountable builder

None of these options is wrong in itself; they do not solve the same problem. Only the last price is mine; the rest describes structures, not rates.

	Internal hire	Agency	Fragmented freelancers	Founder-led build
Time to start	The length of a hiring process, often several months	Pre-sales and team scheduling	Fast, but to coordinate	One to two weeks after agreement
Cost of a v1	A loaded annual salary, committed beyond the v1	The structure (sales, project management, design) is priced in	Variable; the coordination cost is yours	CHF 20’000–45’000 fixed fee for a SaaS v1
Who carries overrun risk	You	Shared, depending on the contract	You	The provider — the price is fixed
Coordination layers	You manage	Project manager, designer, developers	You coordinate each one	None: one person decides and builds
Continuity after the v1	Strong	Maintenance contract	Fragile	Full handover; continuation only when useful
When it is the right choice	The product is the lasting core of the company	Lots of design, content and channels	Well-isolated, already specified tasks	A production v1 with a clear scope, fast, with one owner

The detailed, dimension-by-dimension comparison is in the article Freelancer, agency or independent developer.

05 — Prices

Prices, published

Describe the project: Free. Six questions, an orientation, a personal reply.
Product and architecture diagnostic: CHF 2’400, seven working days, 100% credited against a build signed within 60 days.
Product Rebuild: An outdated or low-performing product, or a prototype that must become production. From CHF 20’000, typically CHF 25’000–80’000, 5 to 10 weeks. A SaaS v1 sits between CHF 20’000 and 45’000. Beyond CHF 80’000, the product is split into phases, each fixed-fee — never a fixed price before a discovery phase.
AI / Automation System: A repetitive information or workflow problem — documents, rules, checks, re-entry. From CHF 20’000, typically CHF 20’000–50’000, 4 to 8 weeks. AI only where it beats a deterministic rule.
Growth Infrastructure: SEO, AEO, GEO, conversion, analytics and the product funnel, built from your data. From CHF 20’000, typically CHF 20’000–40’000, 4 to 6 weeks.
Minimum engagement: CHF 20’000 for any build. Not taken: marketing sites, theme sites, hourly support, native mobile apps, builds under the minimum.
Continuation: Fixed monthly capacity, proposed after launch when it makes sense.

Frequently asked questions

Do you work alone?
Yes. It is a choice: one person accountable for the product, the architecture and the code, with no coordination layer. For brand design or content, I work with identified partners, named in the proposal.
What happens if the project runs late?
If the delay is on my side, the price does not move. If it comes from a dependency on your side (access, content, decisions), the calendar shifts accordingly and the price stays the same.
Do you sign an NDA?
Yes, on request, before any sensitive information or code access is shared.

A project that fits this process?

Describe it in six questions — the reply is personal and arrives within 24 business hours.

Describe your project Or order the diagnostic — CHF 2’400

danilson.daveigaramos.pro@gmail.com · Reply within 24h, Mon–Fri.