scrumlaunch.com valid
ScrumLaunch
A software engineering partner that staffs and runs product teams. Every claim
- Authority
- 46 reach 5 · trust 5 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://www.scrumlaunch.com/llms.txt
- Sections
- 7
- Links
- 39
- Size
- 9206 bytes
- Popularity rank
- #935634
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T18:10:30.576Z
- Last checked
- 2026-10-26T09:07:02.453Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T09:06:52.976Z. Cached copy · Source on scrumlaunch.com
# ScrumLaunch
> A software engineering partner that staffs and runs product teams. Every claim
> on the site is drawn from our own delivery and recruiting records — hours
> logged, team sizes, engagement lengths, and how long hiring actually takes —
> so it can be checked rather than taken on trust.
## How to read our numbers
Hours on the stack pages are attributed through the allocation a developer
worked under rather than through the skills listed on their profile, and they
are a lower bound — about 80–86% of hours since 2023 fall inside an allocation
window, and 51% in 2022. Those pages therefore say "at least". A hiring median
is the number of days from opening a role to a signed offer, measured across
closed vacancies in our applicant tracking system.
## Stacks we staff
- [Hire PHP Developers](https://www.scrumlaunch.com/hire-developers/php-developers): Taking over PHP systems whose original team has gone, moving off end-of-life versions, rewriting a core without rebuilding the product. Our oldest practice.
- [Hire Laravel Developers](https://www.scrumlaunch.com/hire-developers/laravel-developers): Laravel teams on five active client products, from a construction materials marketplace to hospitality. 26-day median from opening a role to a signed offer.
- [Hire React Developers](https://www.scrumlaunch.com/hire-developers/react-js-developers): React teams that hold one codebase for years — four products staffed since 2022. The hours logged, the team sizes and the case studies are on the page.
- [Hire Django Developers](https://www.scrumlaunch.com/hire-developers/django-developers): Django engagements measured in years, not prototypes — three running since 2022. What we built, how big the teams are, and how long hiring takes.
- [Hire WordPress Developers](https://www.scrumlaunch.com/hire-developers/wordpress-developers): Most WordPress work we take on ends as a migration to server-rendered React or Astro — content model kept, URLs preserved. We will say when to stay put.
- [Hire Java Developers](https://www.scrumlaunch.com/hire-developers/java-developers): Java here means a system handling money, audited, with uptime expectations — and a team that has stayed on it. The engagement and its numbers are on the page.
- [Hire iOS Developers](https://www.scrumlaunch.com/hire-developers/ios-developers): Native iOS built by small teams that stay through every OS release and App Store review. Hours logged and team sizes per product, with the case studies.
- [Hire Android Developers](https://www.scrumlaunch.com/hire-developers/android-developers): We are straight about this one: our Kotlin work is deep on few products rather than spread thin. See exactly which, for how long, and with how many engineers.
- [Hire Angular Developers](https://www.scrumlaunch.com/hire-developers/angular-js-developers): Nobody is on Angular here today and the page says so. What we do: keep Angular apps current, or move them to React screen by screen, as we already have.
-
…Machine-readable: GET /v1/resolve?q=scrumlaunch.com · GET /v1/domain/scrumlaunch.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage scrumlaunch.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for scrumlaunch.com:
1. POST https://agentwebmap.com/v1/sites/scrumlaunch.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://scrumlaunch.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/scrumlaunch.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/scrumlaunch.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.