Questions
Clear answers about starting a project, pricing, ownership, source code, support, and what happens next.
No. A short description of what you do, what is difficult today, and what you would like to make easier is enough to begin.
I can help turn that into a clear first scope before development starts.
A few clear sentences are enough.
I review the request and ask any necessary questions.
Then I suggest either a clearly defined first project or a smaller discovery step. Scope, responsibilities, timing, and commercial terms are agreed before development begins.
Yes. BaptizedDragon is an independent practice, so you work directly with the engineer responsible for understanding, building, and supporting the software.
Usually not. Projects range from personal websites and landing pages to operational business software.
A focused project with a clear purpose is often better than trying to build everything at once.
Custom software becomes valuable when everyday work depends on
Yes. Improving, simplifying, or integrating an existing system can be more useful than replacing it.
A complete rewrite is not the default assumption.
No.
Projects may be built for
Some services have published starting prices: Landing Pages start from €101 and Online Shops from €505.
Custom software and other work are scoped separately based on the work involved.
No. Work can begin with one useful, clearly defined result.
Further stages are agreed only when they are needed.
Clearly defined work is normally priced per project or feature.
Ongoing support and continuous improvement can be arranged separately.
Some change is expected. Small clarifications can usually be handled within the work.
Changes that materially affect scope, schedule, or cost are discussed before implementation.
Yes. Whenever practical, work is delivered in visible stages so decisions can be based on working software.
Yes. Clear architecture, conventional technologies, and documentation make the system easier for another capable developer to continue.
Ownership is agreed before development begins. Unless another arrangement is agreed, the client receives full rights to use and operate the delivered software for their business.
Business-specific functionality, visual design, content, and project deliverables are created exclusively for that project. BaptizedDragon retains reusable frameworks, shared libraries, deployment tooling, and other generic components unless a different transfer is agreed.
No. The software is built to remain maintainable and transferable, with conventional infrastructure and documentation so another capable developer can continue it.
Not automatically. Most projects use a commercial licence that allows the client to use and operate the software indefinitely, while reusable generic components remain with BaptizedDragon.
Repository transfer or complete source-code ownership can be agreed before development begins.
Technology is selected according to the problem rather than chosen in advance.
Projects commonly use
Every additional layer increases operational cost and long-term complexity.
The goal is to build the simplest dependable solution that solves the real problem and can continue evolving as the work changes.
Yes. Optional support can cover deployment, monitoring, maintenance, updates, operational improvements, and further development.
Scope and price are agreed separately.
Yes. A website can include semantic HTML, structured metadata, accessibility, strong performance, and crawlable server-rendered content.
These practices support discovery, but rankings and inclusion in AI-generated answers cannot be guaranteed.
You do not need to decide whether the answer is a website, custom software, or automation.
Describe what you want to make easier, and I’ll suggest a practical next step.
Discuss your project