software studio
First we understand the problem. Then we build what works.
We build the software your work calls for — an internal system, a platform, an MVP*, a website, or a new piece of something that already runs. We start with a conversation about the problem and propose the solution that fits it — sometimes a single page, sometimes a whole system. After launch we stay on for support, improvements, new features.
* An MVP is the first working version of a product: the smallest thing real users can actually use, so you learn whether the idea works before the rest gets built.
services
What we help with
You do not have to pick one now. Tell us what the problem is and we will tell you which of the three will do the job — sometimes it is one, sometimes all three, one after the other.
Custom software and platforms
Web applications from scratch — an internal system that replaces a spreadsheet, a platform a whole company runs on, or a first MVP that has to reach real users quickly. We start from the process the software will run and understand it before designing anything; senior engineers do the work end to end, from the data model to the deployment.
- A written scope before the first line of code
- Working software deployed from the first week
- Code, infrastructure and accounts handed over to you
Websites and landing pages
Marketing sites and landing pages, designed from scratch rather than assembled from a template. We first settle who the page is talking to and what the visitor should do, then design around that: statically generated, multilingual where the audience needs it, and fast on a phone connection.
- Design and copy drafted together with you
- Language versions with correct hreflang annotations
- Visibility in search engines and AI assistants: sitemap, structured data, Core Web Vitals
Support and growth
Ongoing work on software that already runs — ours or someone else's: fixes, dependency and framework upgrades, new features, and keeping performance and infrastructure current. We start by reading the code and telling you honestly what shape it is in, before proposing a plan.
- Fixes and upgrades on a regular cadence
- New features in small, reviewable releases
- Analytics and performance watched after launch
portfolio
Software in production
Working software, not mockups. A project appears here once it is live, used every day, and we are free to describe it.
Construction — contractors, subcontractors, investors
Construction Team
constructionteam.app(opens in a new tab)A cloud platform that runs a construction company end to end: tenders and quantity surveys, contracts and price lists, work completion certificates and payment applications, site logs, defect lists and RFIs, plus expenses, revenues, inventory and procurement. Over 40 modules in one system, in place of a folder of spreadsheets and a mailbox.
Result
In production and sold as a subscription with a free trial. The office and the site no longer trade spreadsheets by email — documents, budgets and progress read the same for everyone, in one system.
- 40+ modules: projects, field, accounting, inventory, procurement
- AI recognition and classification of incoming documents
- Interface localised into 12 languages
- Runs in the browser on desktop, tablet and phone — nothing to install
process
How we work
Every project runs the same way: a conversation until the problem is clear, a short written scope, working software every week, a launch you own, and support after it.
Understanding and scope
We start with a call — not about technology, but about what is not working today and what should happen instead. Then we send back a written scope: what gets built, in what order, and what it takes. You approve it before any code exists.
Weekly cycles
You see working software every week, deployed to a real URL rather than shown as screenshots. If we have understood something wrong, it surfaces that same week rather than a month before launch. Priorities can change between cycles — that is why they are short.
Launch
We deploy to production, hand over the code, infrastructure and accounts, and stay close through the first weeks of real traffic.
Growth
After launch you can keep us on for maintenance and new features, or take everything and run it yourself. Nothing is locked to us.
faq
Questions we get asked
Straight answers to what comes up before a project starts. If yours is not here, the contact form is the fastest way to ask it.
- What if I do not know exactly what I need yet?
- That is the normal starting point, and sorting it out is TwoMenCode's job rather than yours. The first call is about the problem, not the technology: what is not working today, who feels it, and what would change if it went away. The written scope comes out of that call with a proposed solution — and if that solution turns out to be smaller or different from what you arrived with, we say so before starting rather than after.
- How long does a project take?
- A landing page or a small marketing site is usually a matter of weeks; a first MVP is typically one to three months, depending on how much has to work on day one. TwoMenCode writes the scope down before starting, so the timeline is agreed rather than guessed, and working software is deployed every week from the first one.
- What does it cost?
- TwoMenCode prices each project on its own, after a written scope — there are no packages or hourly rates published on this site, because the price follows what actually gets built. A landing page and a platform with dozens of modules are different orders of work, so the price comes after the scope call rather than before it. If what you asked for can be done with less, that is where we say so.
- How do we stay in touch during the project?
- You talk to the people who get into the business behind the software, in English or Bulgarian, over whichever channel you already use — email, chat or a call. A question reaches someone who understands why it is being asked and what depends on the answer, so the decision gets made there. Every week ends with working software on a real URL, and that is what the weekly conversation is about.
- Who actually writes the code?
- The code is written by senior engineers at TwoMenCode, from the data model to the deployment. Experience shows in the decisions made early, the ones that are expensive to change later — they are why the software holds up in production rather than only in a demo. The same people sit in the scope conversation, so the decisions in the code are made with the business in mind.
- Can you take over software someone else built?
- Yes — support and growth on software that already runs is one of the three things TwoMenCode does. We start by reading the code and the infrastructure and telling you honestly what shape they are in, even when the answer is not the pleasant one, then work in the same weekly cycles: fixes, dependency and framework upgrades, and new features.
- What happens after launch?
- You own the code, the infrastructure and the accounts, so you can keep TwoMenCode on for maintenance and new features or run everything yourself. Support after launch is a separate agreement, and nothing about the software is locked to us.
contact
Tell us about your project
Send an inquiry and the person who answers gets into the business problem before thinking about software. It does not have to be technical: describe what is not working today, and what to build is something we work out together. Write in English or Bulgarian, whichever you prefer.