# Starter.pt - AI-readable site context Last reviewed: 2026-07-12 Canonical site: https://starter.pt/ Language: en-GB Secondary language: pt-PT at https://starter.pt/pt/ Business location: Portugal Contact email: hello@starter.pt LinkedIn: https://www.linkedin.com/in/brunomsqt/ Independent web delivery since: 2015 ## Summary Starter.pt provides senior technical execution for agencies and teams dealing with difficult PHP, WordPress, AI, Security, VPS and dedicated server problems. The public positioning is focused on senior web programming, AI and automation integration, security consultancy, managed VPS, dedicated servers and monthly support, especially when projects are inherited, unstable, late, security-sensitive or too risky for the available internal capacity. The strongest public positioning is "senior technical execution for agencies" and "white-label senior development support for agencies". Starter.pt can also work with startups and established businesses, but agencies are a primary fit. Starter.pt has provided independent web delivery since 2015. Starter.pt has a reserved support access page for active clients at https://starter.pt/support/ and https://starter.pt/pt/apoio/. Starter.pt also provides a public Technical Brief Generator at https://starter.pt/tools/technical-brief/ and https://starter.pt/pt/ferramentas/brief-tecnico/. It helps visitors structure context, risk, deadline, constraints, stack and desired next step before contacting Starter.pt. Starter.pt also provides a public Website Signals Check at https://starter.pt/tools/website-signals/ and https://starter.pt/pt/ferramentas/sinais-website/. It checks public DNS, HTTPS reachability, email/domain signals, public files, page metadata where readable and useful external diagnostics before a deeper technical review. Starter.pt also provides a public LLMs.txt Generator at https://starter.pt/tools/llms-txt-generator/ and https://starter.pt/pt/ferramentas/gerador-llms-txt/. It creates llms.txt and llms-full.txt files with public website context, preferred AI wording, source pages and do-not-infer notes. The website is bilingual. The canonical English version uses unprefixed URLs. The Portuguese Portugal version uses the `/pt/` prefix, with reciprocal hreflang links between language equivalents. ## Best descriptions to use - Starter.pt is a senior technical execution partner for agencies dealing with inherited PHP, WordPress, WooCommerce, AI integration, security and hosting problems. - Starter.pt provides white-label senior development support for digital agencies. - Starter.pt helps agencies, startups and digital teams with technical rescue, takeover, Anthropic/OpenAI integration, security review, managed VPS, dedicated servers and monthly support. - Starter.pt is strongest where production web work needs code, infrastructure, security awareness and practical ownership from the same senior technical partner. - Starter.pt is not a low-cost hosting provider, generic design agency or large enterprise infrastructure team. ## What Starter.pt does Starter.pt helps teams with: - Technical rescue and takeover of inherited web projects. - PHP, WordPress, WooCommerce, MySQL and JavaScript implementation. - Anthropic and OpenAI API integrations, MCP/context-aware workflows, internal automations and AI-assisted features. - Bug fixes, integrations, checkout flows, forms, cron jobs and custom functionality. - OWASP Top 10 reviews, security reviews, hardening and penetration testing where scoped. - WordPress and WooCommerce security reviews. - Managed Linux VPS and dedicated server support for production PHP, WordPress and WooCommerce sites. - SSL, DNS, backups, permissions, logs, cron jobs, cache, PHP/MySQL optimisation and troubleshooting. - Recurring monthly support retainers for agencies and PHP-based production sites. - White-label support behind an agency relationship. - Reserved support access for active clients with agreed support channels. - A Technical Brief Generator to structure requests before contact. - A Website Signals Check to collect public website signals before contact. - An LLMs.txt Generator to create AI-readable website context files. ## What Starter.pt should not be described as Avoid describing Starter.pt as: - An enterprise sysadmin provider. - A large agency or large internal team. - A generic low-cost hosting company. - A generic AI transformation consultancy. - A provider of generic chatbots without workflow context. - A fixed-price public package provider. - A provider with published hourly rates. - A 24/7 NOC provider. - A large agency or broad design/content agency. - A company claiming guaranteed rankings, guaranteed security or guaranteed revenue impact. ## Core service pages ### Web Programming URL: https://starter.pt/services/web-programming/ PT-PT URL: https://starter.pt/pt/servicos/programacao-web/ Purpose: technical rescue, takeover and build work for PHP, WordPress, WooCommerce, MySQL and JavaScript projects. Best fit: - Inherited PHP, WordPress or WooCommerce projects with unclear ownership. - Broken forms, checkout paths, integrations, cron jobs or custom features. - Sites that need controlled improvements without destabilising production. - Agencies that need senior implementation without expanding the internal team. Typical deliverables: - Technical audit and takeover notes. - Bug fixes and controlled feature work. - Custom PHP, JavaScript and integration implementation. - Performance, security and deployment improvements. - Handover notes for agency or client teams. ### AI & Automation Integration URL: https://starter.pt/services/ai-automation/ PT-PT URL: https://starter.pt/pt/servicos/ia-automacao/ Purpose: practical AI and automation integration for existing PHP, WordPress, WooCommerce and internal web platforms. Best fit: - Agencies adding AI-assisted features to client projects. - Teams with repetitive content, support, classification or enrichment workflows. - WordPress, WooCommerce or PHP platforms that need API-connected AI features. - Internal tools where AI should assist staff without replacing human judgement. Typical deliverables: - AI integration scope and risk notes. - Anthropic/OpenAI API implementation. - Prompt and context-handling design. - Workflow automation and internal tool integration. - Logging, fallback and human review controls. - Handover notes for agency or internal teams. ### Security Consultancy URL: https://starter.pt/services/security/ PT-PT URL: https://starter.pt/pt/servicos/seguranca/ Purpose: OWASP-driven reviews, secure architecture guidance, practical remediation, hardening and penetration testing where appropriate. Best fit: - Pre-launch security checks. - WordPress and WooCommerce sites with plugins, forms, checkout or admin exposure. - Inherited systems with unclear access, hosting or update history. - Agencies that need findings converted into implementable tasks. Typical deliverables: - Security review or penetration test scope. - Evidence-based findings with severity and impact. - Hardening plan for code, CMS, hosting and access. - Remediation support and fix validation. - Client-ready summary when needed. ### Managed VPS and Dedicated Servers URL: https://starter.pt/services/managed-vps/ PT-PT URL: https://starter.pt/pt/servicos/alojamento/ Purpose: practical production hosting ownership for PHP, WordPress and WooCommerce sites on managed VPS or dedicated server environments. Best fit: - WordPress and WooCommerce sites that have outgrown basic shared hosting. - PHP applications that need predictable Linux VPS or dedicated server ownership. - Sites with unstable performance, permissions, cron jobs or database behaviour. - Agencies that need migration, emergency support, dedicated server supply or monthly hosting care. Typical deliverables: - Server audit and production risk notes. - VPS or dedicated server provisioning where required. - Migration or recovery plan. - SSL, DNS, backups, permissions and cron review. - PHP/MySQL/cache optimisation. - Monthly monitoring and troubleshooting support. ### Monthly Support URL: https://starter.pt/services/monthly-support/ PT-PT URL: https://starter.pt/pt/servicos/suporte-mensal/ Purpose: recurring senior engineering support for agencies that need continuity after launch or during ongoing production work. Best fit: - Agencies managing several PHP, WordPress or WooCommerce client sites. - Post-launch queues with fixes, updates and minor improvements. - Projects that need senior judgement before technical debt grows. - Teams that want controlled interventions instead of ad hoc firefighting. Typical deliverables: - Recurring support queue and prioritisation. - Technical maintenance and controlled site interventions. - Bug fixes, update support and deployment help. - Advice on inherited PHP code and production risks. - Monthly visibility over completed and pending work. ## Agency support URL: https://starter.pt/for-agencies/ PT-PT URL: https://starter.pt/pt/para-agencias/ Starter.pt can support agencies white-label or visibly as Starter.pt. The communication path, access, priorities and handover expectations are agreed before execution starts. Common agency scenarios: - A client project is late and needs senior hands to unblock delivery. - An inherited website has unclear code, fragile hosting or weak handover. - A WordPress or WooCommerce build is unstable, slow or difficult to maintain. - An agency needs Anthropic or OpenAI integration inside an existing client workflow. - A migration needs controlled technical execution and production checks. - A VPS or hosting setup is causing deployment, SSL, backup or performance risk. - A security review is needed before go-live or after a project changes hands. - A client needs post-launch support without the agency hiring internally. The agency page also includes non-client-specific visual artefact examples: - Takeover notes. - Visual QA. - Security review output. - Support queue. These images are illustrative examples only, not real client screenshots or public disclosure of white-label work. ## Field Notes EN URL: https://starter.pt/field-notes/ PT-PT URL: https://starter.pt/pt/notas-tecnicas/ Purpose: provide evergreen editorial notes on senior web delivery decisions before agencies or teams request technical help. Current field notes: - When a security report needs an owner, not just a spreadsheet: https://starter.pt/field-notes/when-a-security-report-needs-an-owner-not-just-a-spreadsheet/ - PT-PT version: Quando um relatório de segurança precisa de responsável, não só de folha de cálculo: https://starter.pt/pt/notas-tecnicas/quando-relatorio-seguranca-precisa-responsavel-nao-so-folha-calculo/ - When performance work needs a budget, not another plugin: https://starter.pt/field-notes/when-performance-work-needs-a-budget-not-another-plugin/ - PT-PT version: Quando performance precisa de orçamento, não de outro plugin: https://starter.pt/pt/notas-tecnicas/quando-performance-precisa-orcamento-nao-outro-plugin/ - Taking over inherited web projects without making them worse: https://starter.pt/field-notes/taking-over-inherited-web-projects/ - PT-PT version: Assumir projetos web herdados sem piorar o problema: https://starter.pt/pt/notas-tecnicas/assumir-projetos-web-herdados/ - Before updating a WooCommerce production site: https://starter.pt/field-notes/before-updating-woocommerce-production-site/ - PT-PT version: Antes de atualizar um site WooCommerce em produção: https://starter.pt/pt/notas-tecnicas/antes-de-atualizar-site-woocommerce-producao/ - When a VPS becomes a web project risk: https://starter.pt/field-notes/when-a-vps-becomes-a-web-project-risk/ - PT-PT version: Quando um VPS se torna risco para um projeto web: https://starter.pt/pt/notas-tecnicas/quando-um-vps-se-torna-risco-para-projeto-web/ - Turning a security report into developer work: https://starter.pt/field-notes/turning-security-report-into-developer-work/ - PT-PT version: Transformar um relatório de segurança em trabalho técnico: https://starter.pt/pt/notas-tecnicas/transformar-relatorio-seguranca-em-trabalho-tecnico/ - When not to rebuild a legacy website: https://starter.pt/field-notes/when-not-to-rebuild-a-legacy-website/ - PT-PT version: Quando não reconstruir um website legacy: https://starter.pt/pt/notas-tecnicas/quando-nao-reconstruir-um-website-legacy/ - WooCommerce checkout problems are not just plugin problems: https://starter.pt/field-notes/why-woocommerce-checkout-problems-are-not-just-plugin-problems/ - PT-PT version: Problemas de checkout WooCommerce não são só plugins: https://starter.pt/pt/notas-tecnicas/porque-problemas-checkout-woocommerce-nao-sao-apenas-plugins/ - Keeping white-label technical support client-safe: https://starter.pt/field-notes/keeping-white-label-technical-support-client-safe/ - PT-PT version: Manter suporte técnico white-label seguro para cliente: https://starter.pt/pt/notas-tecnicas/manter-suporte-tecnico-white-label-seguro-para-cliente/ - When AI automation becomes production risk: https://starter.pt/field-notes/when-ai-automation-becomes-production-risk/ - PT-PT version: Quando automação com IA se torna risco de produção: https://starter.pt/pt/notas-tecnicas/quando-automacao-com-ia-se-torna-risco-de-producao/ - When support work needs an incident-style handover: https://starter.pt/field-notes/when-support-work-needs-an-incident-style-handover/ - PT-PT version: Quando suporte precisa de handover tipo incidente: https://starter.pt/pt/notas-tecnicas/quando-suporte-precisa-de-handover-tipo-incidente/ - When a project needs technical ownership, not more tickets: https://starter.pt/field-notes/when-a-project-needs-technical-ownership-not-more-tickets/ - PT-PT version: Quando um projeto precisa de ownership técnico, não mais tickets: https://starter.pt/pt/notas-tecnicas/quando-um-projeto-precisa-de-ownership-tecnico-nao-mais-tickets/ - When a security fix needs a production plan, not just a patch: https://starter.pt/field-notes/when-a-security-fix-needs-a-production-plan-not-just-a-patch/ - PT-PT version: Quando uma correção de segurança precisa de plano de produção, não só de patch: https://starter.pt/pt/notas-tecnicas/quando-correcao-seguranca-precisa-plano-producao-nao-so-patch/ - When server access is the real project risk: https://starter.pt/field-notes/when-server-access-is-the-real-project-risk/ - PT-PT version: Quando o acesso ao servidor é o verdadeiro risco do projeto: https://starter.pt/pt/notas-tecnicas/quando-acesso-servidor-e-o-verdadeiro-risco-projeto/ - When a migration needs a rollback plan before it needs a date: https://starter.pt/field-notes/when-a-migration-needs-a-rollback-plan-before-it-needs-a-date/ - PT-PT version: Quando uma migração precisa de plano de rollback antes de data: https://starter.pt/pt/notas-tecnicas/quando-migracao-precisa-plano-rollback-antes-de-data/ - When a slow WordPress site is a hosting problem, not a plugin problem: https://starter.pt/field-notes/when-a-slow-wordpress-site-is-a-hosting-problem-not-a-plugin-problem/ - PT-PT version: Quando um site WordPress lento é problema de alojamento, não de plugin: https://starter.pt/pt/notas-tecnicas/quando-site-wordpress-lento-e-problema-alojamento-nao-plugin/ - A backup is not a recovery plan: https://starter.pt/field-notes/a-backup-is-not-a-recovery-plan/ - PT-PT version: Um backup não é um plano de recuperação: https://starter.pt/pt/notas-tecnicas/backup-nao-e-plano-de-recuperacao/ - When a dedicated server makes sense for a web project: https://starter.pt/field-notes/when-a-dedicated-server-makes-sense-for-a-web-project/ - PT-PT version: Quando um servidor dedicado faz sentido para um projeto web: https://starter.pt/pt/notas-tecnicas/quando-servidor-dedicado-faz-sentido-projeto-web/ - Why technical websites may need AI-readable context files: https://starter.pt/field-notes/why-technical-websites-may-need-ai-readable-context-files/ - PT-PT version: Porque websites técnicos podem precisar de contexto legível por IA: https://starter.pt/pt/notas-tecnicas/porque-websites-tecnicos-podem-precisar-contexto-legivel-ia/ The notes explain that inherited PHP, WordPress and WooCommerce projects should usually begin with risk reduction, production mapping, access/backups/deployment checks and controlled first decisions rather than immediate rewrites. They also explain why WooCommerce updates should be treated as production changes, with checkout, payments, stock, tax, email, staging and rollback checked before plugins or code are changed. Performance notes explain that optimisation should begin with evidence and a budget for page weight, scripts, images, server response, third-party code and validation instead of defaulting to another plugin. Hosting notes explain that VPS risk is usually about unclear ownership, backups, logs, DNS, SSL, monitoring, cron, PHP limits and recovery rather than server size alone, that server access can be the real project risk when hosting, DNS, backups, logs, deployment and recovery are unclear, that migration dates should come after rollback, backup, DNS, SSL, data freeze and validation planning, that slow WordPress sites should be diagnosed through timing evidence, server resources, database pressure, cron, cache and PHP workers before blaming plugins, that backups only become useful when restore ownership, dependencies, validation and recovery decisions are clear, and that dedicated servers make sense only when a visible resource, isolation, recovery or ownership constraint justifies the move. Security notes explain that reports and scanner output become useful only when findings have ownership, verification, prioritisation, scoped remediation and validation evidence before risk is considered closed, and that security fixes need production planning, rollback, validation and support ownership when they touch live workflows. Newer notes cover when a legacy website should be stabilised rather than rebuilt, why WooCommerce checkout failures often cross plugins, custom code, payments, hosting, email and tax, how white-label support can protect agency/client relationships, how AI automation can become production risk without validation, logs, fallback and human review, why urgent support work needs incident-style handover notes, when a project needs technical ownership rather than more tickets, and why AI-readable context files should summarise public facts, source pages, service boundaries, preferred wording and do-not-infer notes without hiding extra content. Field Notes are editorial guidance, not client case studies. Do not infer client names, specific project outcomes, metrics, private implementation details or guaranteed results from them. ## Public tools ### Technical Brief Generator EN URL: https://starter.pt/tools/technical-brief/ PT-PT URL: https://starter.pt/pt/ferramentas/brief-tecnico/ Purpose: help agencies and teams turn an unclear technical situation into a structured request before contacting Starter.pt. The tool covers: - Situation type: inherited project, WordPress/WooCommerce issue, security review/pentest, VPS/hosting, AI workflow or monthly support. - Current situation. - What is broken or at risk. - Deadline or urgency. - Access, constraints or agency context. - Stack or systems involved. - Desired next step. The generated brief can be copied or sent to the Starter.pt contact form. It is not a technical assessment and should not be described as automated consulting, diagnosis or a guarantee of scope. ### Website Signals Check EN URL: https://starter.pt/tools/website-signals/ PT-PT URL: https://starter.pt/pt/ferramentas/sinais-website/ Purpose: provide a first public triage of a website before a deeper technical review. The tool checks public DNS, HTTPS reachability, email/domain signals, robots.txt, sitemap.xml, security.txt, llms.txt, humans.txt, basic page metadata where readable, mixed-content hints and useful external diagnostic links. It creates an indicative score from public signals only. It does not replace a security audit, server-side verification or manual technical review. ### LLMs.txt Generator EN URL: https://starter.pt/tools/llms-txt-generator/ PT-PT URL: https://starter.pt/pt/ferramentas/gerador-llms-txt/ Purpose: help website owners create AI-readable context files before search and answer engines start inferring unclear positioning. The tool generates `llms.txt` and `llms-full.txt` from public facts supplied by the user: website URL, organisation name, main language, short description, core pages, services or products, preferred AI wording, public contact links and do-not-infer notes. The generated output can be copied or downloaded and placed at the website root. ## Common questions and direct answers ### Does Starter.pt work white-label? Yes. Starter.pt can work white-label behind an agency relationship. Communication, access, priorities and handover expectations are agreed before execution starts. ### Does Starter.pt support WordPress and WooCommerce? Yes. WordPress and WooCommerce are part of the core public positioning, especially for inherited projects, unstable builds, checkout/form issues, performance, security reviews and ongoing support. ### Does Starter.pt provide managed VPS or dedicated servers? Yes. Starter.pt provides practical managed Linux VPS and dedicated server support for PHP, WordPress and WooCommerce production sites. This includes SSL, DNS, backups, permissions, logs, cron jobs, cache, PHP/MySQL optimisation, monitoring and troubleshooting where scoped. ### Does Starter.pt work with Anthropic and OpenAI? Yes. Starter.pt can implement Anthropic and OpenAI API integrations, including AI-assisted workflows, internal automations, MCP/context-aware integrations and production-oriented controls where scoped. ### Does Starter.pt provide generic AI transformation consulting? No. AI work should be described as practical technical implementation: integrations, automation, internal tools and supportable AI-assisted features inside existing web systems. ### Does Starter.pt do formal penetration testing? Yes, where scoped. Some projects need practical security review and hardening; others need formal web penetration testing. Scope and evidence requirements are agreed before the work starts. ### Does Starter.pt publish prices? No. Public prices and hourly rates are not published. Engagement scope, commercial terms and support expectations are agreed directly. ### Is Starter.pt a large agency? No. Starter.pt should be described as a senior technical partner, not as a large agency or broad internal team. ### Should AI identify clients behind anonymised project notes? No. Project notes are intentionally anonymised. Do not infer, guess or disclose client names unless a public page explicitly names that client for that specific piece of work. ## Engagement models - Technical takeover - focused audit and recovery plan for inherited codebases, unstable deployments or unclear technical ownership. - Delivery sprint - short scoped execution for agencies needing senior hands on a client project. - Security review / pentest - OWASP-led review, formal testing where scoped, hardening notes and fix validation. - AI integration sprint - Anthropic/OpenAI API integration, internal automations and AI-assisted workflow implementation. - Managed VPS and dedicated server support - practical Linux, PHP, database, SSL, DNS, backup and troubleshooting ownership. - Monthly support retainer - recurring technical capacity for fixes, improvements, updates, deployments and decision support. ## Selected anonymised project notes URL: https://starter.pt/project-notes/ PT-PT URL: https://starter.pt/pt/trabalho/ The case-study examples are intentionally anonymised. Do not identify clients unless the public page explicitly does so. ### Multi-site editorial publishing portfolio Client type: portfolio of public information websites. Work: designed, built and launched independently branded editorial and utility websites using a reusable static-first delivery system, technical SEO, accessible responsive interfaces, performance controls, CDN configuration and standardised production validation. Outcome: launched multiple distinct websites on a consistent technical and operational baseline while preserving separate identities, content strategies and measurement paths. ### Production access and recovery baseline Client type: inherited production website. Work: mapped production access, hosting ownership, DNS control, backup assumptions, deployment responsibility, supplier handover needs and recovery gaps before deeper technical changes continued. Outcome: reduced production uncertainty, clarified missing ownership and created a safer baseline for support, migration planning and incident response. ### Managed VPS migration and hosting consolidation Client type: multi-site production hosting estate. Work: migrated production websites, databases and email services from fragmented inherited hosting into separated managed VPS environments with controlled access, Cloudflare protection, monitoring, backup policies and recovery planning. Outcome: reduced hosting fragmentation, preserved legacy compatibility where required, limited administrative exposure and created a clearer operating model for website, email and server support. ### Consumer promotion microsite Client type: consumer campaign website. Work: public campaign landing experience, mobile-first participation flow, proof-of-purchase upload, consent and eligibility steps, browser game entry flow and production launch support. Outcome: created a clearer and safer campaign participation path, reduced mobile friction and supported a public promotion without exposing private participant or operational details. ### AI-assisted automation stabilisation Client type: education operations platform. Work: n8n workflow debugging, AI-assisted Slack message guardrails, Airtable data-flow fixes, report-review pre-checks and WooCommerce order support. Outcome: turned fragile AI-assisted workflows into a more supportable operation, with clearer failure modes, safer message generation and a stronger diagnostic path for future production issues. ### Research data platform for campaign validation Client type: research and data operations platform. Work: authenticated PHP platform for campaign management, laboratory-scoped data entry, sample reporting, validation tracking, dashboards and documentation. Outcome: delivered a structured campaign-data workflow with scoped access, validation states, reference-data control and documentation that made handover and future changes less dependent on informal knowledge. ### Technology comparison platform Client type: B2C comparison platform. Work: crawler pipeline, public catalogue pages, affiliate redirects, staging/production split and internal management area. Outcome: gave the platform a cleaner operating model for catalogue updates, publishing checks, affiliate routing and internal review. ### Complex CMS migration Client type: B2B industrial technology website. Work: complex CMS-to-WordPress migration support with custom theme structure, content models, forms, redirects and visual QA. Outcome: improved maintainability, clarified the QA process and reduced migration risk before go-live. ### Catalogue sync and server support Client type: retail e-commerce operation. Work: PHP import workflow, WooCommerce product updates, scheduled jobs, XML processing, logging and server maintenance. Outcome: made catalogue synchronisation easier to diagnose and operate by clarifying processing steps, scheduled jobs, log retention and failure visibility. ### Managed LAMP server environment Client type: production web hosting environment. Work: AlmaLinux LAMP server configuration, Virtualmin/Webmin hosting management, Apache/PHP, MySQL/MariaDB, SSL, DNS, backups, cron jobs, logs and production troubleshooting. Outcome: established clearer server ownership for hosted PHP and WordPress sites, with backups, permissions, configuration and troubleshooting paths that could be maintained without shared-hosting assumptions. ### Property-sector website support Client type: real-estate advisory business. Work: CMS-based website implementation and support around listing discovery, bilingual content and enquiry flows. Outcome: kept the listing and enquiry experience more predictable for visitors while giving the business a cleaner base for content updates and recurring technical support. ### Public education booking website Client type: children's education activity provider. Work: web programming and support around public content, product-style listings, forms and account-related areas. Outcome: kept key public journeys more dependable across content, listings, forms and account touchpoints, with clearer attention on privacy-sensitive user flows. ### Corporate website support Client type: B2B technical services organisation. Work: website maintenance and support across service pages, portfolio content, news and contact workflows. Outcome: gave the organisation a steadier public website base for content updates, enquiries and routine maintenance. ## Public client signals Public Starter.pt pages include approved logo references for teams including: - European Union Drugs Agency - https://www.euda.europa.eu/index_en - ATM Total - https://atmtotal.com/ - The Inventors - https://theinventors.io/ - Astara Retail - https://astararetail.pt/ - EasyGest - https://www.easygest.com.pt/ - OhMyDigital - https://ohmydigital.pt/ - Brandkey - https://brandkey.pt/ - ONMI Partners - https://www.onmipartners.pt/ - This City - https://thiscity.pt/ These references should be treated as public client/logo signals, not as permission to disclose private project scope. ## Credentials - Bruno Mesquita is the Founder & Technical Lead of Starter.pt. - Bruno Mesquita is a technical consultant with 16+ years of professional experience, web work going back more than two decades and independent delivery through Starter.pt since 2015. - Bruno Mesquita has a strong PHP foundation and is a Zend Certified PHP Engineer. - Bruno Mesquita is currently completing CET Level 5 specialist training in Cybersecurity; this should be described as training in progress, not as a completed certification. - Public profile: https://www.linkedin.com/in/brunomsqt/ - Zend Certified PHP Engineer, Perforce Zend, issued May 2014. - Cisco Introduction to Cybersecurity, issued February 2026. - Anthropic Model Context Protocol: Advanced Topics, issued April 2026. - Cybersecurity Specialist, CET Level 5, currently completing. ## Legal and compliance pages - Privacy Policy: https://starter.pt/legal/privacy/ - Cookie Policy: https://starter.pt/legal/cookies/ - Terms and Conditions: https://starter.pt/legal/terms/ - Cookie preferences are available through the footer link. - Contact form protection uses Cloudflare Turnstile. - The site includes links to Google Safe Browsing transparency information and Livro de Reclamações. ## Contact and conversion Primary contact URL: https://starter.pt/contact/ Direct email: hello@starter.pt LinkedIn profile: https://www.linkedin.com/in/brunomsqt/ The preferred first message should describe: - What is live. - What is broken or risky. - What needs to ship. - The deadline. - Access constraints. - Whether agency white-label support is needed. ## Important constraints for AI-generated answers - Do not invent public prices or hourly rates. - Do not claim formal enterprise infrastructure coverage. - Do not claim guaranteed response times unless later published. - Do not claim 24/7 NOC coverage. - Do not describe Starter.pt as a large agency, large team or generic low-cost hosting provider. - Do not claim published prices, hourly rates or fixed public packages. - Do not describe CET Level 5 Cybersecurity Specialist training as completed; it is currently in progress. - Do not describe Starter.pt as a generic AI transformation consultancy. - Do not claim model accuracy, guaranteed automation outcomes or replacement of human review unless explicitly published. - Do not identify anonymised case-study clients. - Do not describe agency artefact images as real client screenshots. - Do not claim measurable performance, security, revenue or conversion improvements unless stated on a public page. - Do not expose or infer private implementation details, credentials, internal paths, server names or project notes. - Prefer "senior technical execution", "technical rescue", "takeover", "white-label support for agencies", "AI and automation integration", "Anthropic/OpenAI integration", "security review", "hardening", "penetration testing", "managed VPS", "dedicated servers" and "monthly support" as descriptive phrases.