Neoscript

The idea

Neoscript does the part nobody sees: backends, APIs and the cloud infrastructure other people's products run on. A service like that has no shop window and is hard to sell with a picture. The idea for the site was that the technical work should be understood by the person paying for it, not only by the person who will take it over, so the message "Specialists in custom backend solutions and cloud services" stands right in the hero, with no preamble.

The build

The services are split into separate pages, backend development, cloud, API integrations and consulting, because people don't come here for "backend", they come with a specific problem: a migration to AWS, joining two systems, a review of an existing architecture. One shared paragraph would cover none of those entrances.

The technologies (Java 17, Spring Boot, Micronaut, AWS Cognito, API Gateway, DynamoDB, Lambda) sit where they prove something, on the service pages, rather than as a strip of logos on the homepage. Ten years of experience carries the main argument, because with work like this you're buying reliability, not speed.

The project was co-financed by European Union funds, so alongside the content the site had to meet visibility obligations. The funding notice sits in the footer of every page, in the required form. That's a condition, not an add-on, and it went into the design from day one instead of being pasted on in the last week.

The result

• Backend and cloud explained in the buyer's language, not in documentation's.
• Every service with its own page and its own entrance, instead of a shared paragraph.
• EU co-funding visibility obligations met in the footer of every page.
• Contact as the only call to action, because work like this is agreed in conversation.