Services
Services
I'm one developer, so I take on a limited number of projects at a time and you deal with me from the first conversation to handover. Every project ships with the same safety baseline, in plain words: protections your browser enforces on every page, only the code that is needed, every form checked on the server, and no passwords or keys left in the code.
Start a project and I reply with questions and a written plan.
Websites
Deliverables
- A fast website that works well on phones and with assistive tools, built from fixed pages wherever your content allows (cheaper to run and harder to attack).
- Browser protections (security headers, including a Content-Security-Policy) set up and tested.
- Clean SEO fundamentals: semantic HTML, titles and descriptions, a sitemap.
Your inputs
- Your content, or a clear brief if you want help structuring it.
- Access to your domain and hosting, or a decision on where to host.
- One person who can give feedback and approve changes.
Boundaries
- Content is structured and edited, not authored. Copywriting and photography are out of scope.
- Fixed pages are not right for everything. Logins or a database make it a web app.
Will you host it for me?
The site is set up on hosting you own and control, so there is no lock-in.
Web apps
Deliverables
- A custom web app built for one specific job: an internal tool, a booking system, a dashboard, a client portal.
- Sign-in, access rules (who may see or change what) and checks on everything users send, designed in from the start.
- The source code, with notes on how to run it and automated checks.
Your inputs
- A clear description of the problem and the people who will use the app.
- Example data, or a description of it. Real personal data is not exchanged until handling is agreed.
- Decisions on hosting and accounts, which you own.
Boundaries
- Focused applications are the fit. Very large systems are outside what I take on.
- Support is business-hours only; response times are in the engagement terms.
Who owns the code?
You own the custom code and design created for you once paid in full. See the engagement terms.
Android and iOS apps
Deliverables
- A mobile app for Android, iOS, or both.
- A straight recommendation on whether a native app is needed at all, or whether a web app you can install on the phone (a PWA) would do. See how to choose.
- Safe defaults: no secrets inside the app, careful storage on the phone, and server checks that do not trust the app.
Your inputs
- Your own Apple Developer and Google Play developer accounts, so the app is published under your name. Apple and Google charge for these.
- Test devices or testers on the platforms you need.
- Store listing content: name, description, screenshots approval, privacy policy.
Boundaries
- App store approval is decided by Apple and Google. Approval and its timing cannot be guaranteed.
- Supporting both platforms takes more time than one.
Do I need a native app?
Not always. A PWA can be installed and work offline from one codebase. The recommendation follows what your users and features actually need.
Tools and automation
Deliverables
- Focused tools and scripts that do one job well, in the spirit of the open-source project recall.
- Open source or private, your choice.
- Documentation for running and maintaining it.
Your inputs
- A clear description of the task and the current workflow.
- Sample inputs and expected outputs.
- Someone who will own the tool afterwards.
Boundaries
- Tools need maintenance. They are kept small so you can maintain them.
- Automation handles known patterns. It does not replace human judgement.
Can the tool be open source?
Yes, if you want. Open-source components always stay under their own licences.
Personal security
Setup help for your own accounts and devices. The personal security page explains what a session covers.
Deliverables
- Hands-on setup for individuals and small businesses: password manager, two-factor authentication, backups.
- Device hardening and phishing basics, explained in plain language.
- Small tools for personal security, like the free tools on this site.
Your inputs
- Your devices and accounts available during the session.
- Time to set things up properly. Rushed security setup gets undone.
Boundaries
- This is setup and advice. It is not incident response, and it is not a guarantee that nothing bad will happen.
- If you think you have been hacked or are being targeted, you are pointed to the right official help.
Do you need my passwords?
No. You type them. They are never requested.
How pricing works
I do not publish a price list, because two sites that look alike can differ a great deal in the work behind them. This is how a price is reached.
- A written quote before any work starts. After we talk, you get the scope and the price in writing. The price is for that defined scope, not an hourly meter.
- What moves the price. The number of pages or screens, whether people sign in, what data it handles, connections to other services (payments, email, maps), how much of the content I have to structure, and the deadline.
- Costs that are yours, paid to the provider. Domain name, hosting, Apple and Google developer accounts, and any paid third-party tools are bought in your name, at the provider's price.
- Changes after the plan is agreed. I quote them separately before I start them, so there are no surprises.
- A rough range helps. The budget box on the project form is optional. If you are unsure, leave it blank and we talk.
Engagement terms
- Revisions and handover
- Two rounds of revisions during the build. A 30-day bug-fix window after launch for issues in what was delivered; new features are scoped separately. One handover walkthrough call of up to 60 minutes.
- Support response
- I acknowledge messages within 1 business day. If something delivered is down or has a security issue, acknowledgement is aimed at within 4 business hours (IST). Support is business-hours only.
- Ownership
- You own the custom code and design created for you once paid in full. I keep my pre-existing tools, libraries and general know-how. Open-source components stay under their own licences.
- Your enquiry
- Contact and project-brief messages are kept for 12 months, then deleted, or sooner on request. See privacy.
- Reply time
- I reply to new enquiries within 2 business days.
These are the default terms. A written agreement governs each project.
What happens if I find a bug after launch?
Report it within 30 days and issues in delivered work are fixed. After that, or for new features, the work is scoped separately.
How fast is the response if my site goes down?
Acknowledgement is aimed at within 4 business hours (IST) for something I built. Support is business-hours only.
Do I get the source code?
Yes. Once paid in full, you own the custom code and design made for you.
Have a project in mind?
Send a short brief. I reply to new enquiries within 2 business days.