---
title: "How to Build a Web Development Team: Roles, Structure, Hiring, and Engagement Models"
url: "https://www.monocubed.com/blog/web-development-team/"
date: "2026-05-13T11:27:52+00:00"
modified: "2026-05-13T11:27:54+00:00"
author:
  name: "Yuvrajsinh Vaghela"
  url: "https://www.monocubed.com/"
categories:
  - "Web Development"
word_count: 4207
reading_time: "22 min read"
summary: "Most web projects don't miss budget or deadline because of bad code. They miss because the wrong web development team was assembled. A founder hires two developers and a designer, ships a working h..."
description: "A complete guide to building a web development team. Learn the core roles, team sizes by project stage, in-house vs outsourced models, and hiring tips."
keywords: "Web Development Team, Web Development"
language: "en"
schema_type: "Article"
related_posts:
  - title: "Typescript vs JavaScript: Why Choose Typescript Over JavaScript?"
    url: "https://www.monocubed.com/blog/typescript-vs-javascript/"
  - title: "Top 10 Node.js Development Companies [Reviewed and Ranked]"
    url: "https://www.monocubed.com/blog/nodejs-development-companies/"
  - title: "Website Design Cost: A Complete Guide for Businesses [Detailed Pricing Breakdown]"
    url: "https://www.monocubed.com/blog/website-design-cost/"
---

# How to Build a Web Development Team: Roles, Structure, Hiring, and Engagement Models

_Published: May 13, 2026_  
_Author: Yuvrajsinh Vaghela_  

![How to build a web development team](https://www.monocubed.com/wp-content/uploads/2026/05/How-to-build-a-web-development-team.jpeg)

Most web projects don’t miss budget or deadline because of bad code. They miss because the wrong web development team was assembled. A founder hires two developers and a designer, ships a working homepage in week six, then watches the schedule slip once testing, deployment, stakeholder reviews, and AI integrations enter the picture.

According to[ Mordor Intelligence](https://www.mordorintelligence.com/industry-reports/web-development-market), **the global web development market is projected to grow from USD 80.6 billion in 2025 to USD 134.17 billion by 2031, a CAGR of 8.87%, with AI-powered web applications driving much of the demand.** That surge makes building the right team mix, with AI experience, harder than ever.

The roles that get cut first, usually QA, DevOps, AI engineers, and a project manager, are the same ones that cost the most to add back later. Teams staffed with only generalists rediscover this every quarter when releases slip, and regressions reach production.

This guide covers the core roles a modern[ AI web development company](https://www.monocubed.com/services/ai-development/) staffs, how website team structure scales with project stage, the in-house versus outsourced trade-offs, and the engagement options that fit each setup. Let’s start with the foundational definition.

## What a Web Development Team Is and What Modern Teams Actually Build
A web development team is a structured group of specialists who plan, design, build, test, deploy, and maintain a website or web application together. The team usually includes a project manager, designer, front-end and back-end developers, and a QA engineer.

Additional roles, like a business analyst, solution architect, DevOps engineer, AI/ML engineer, and SEO specialist, join as the project grows. The same group goes by website development team, web developer team, or web agency team. Composition always beats raw headcount.

Every modern web project covers rendering, routing, data, security, testing, deployment, and increasingly AI integrations, and those building blocks shape the team. Our deeper guide on the[ fundamentals of web development](https://www.monocubed.com/blog/fundamentals-of-web-development/) walks through the layers every team has to own.

### Why composition beats headcount
A four-person team with full role coverage outperforms a seven-person team of generalists almost every time. Coverage means each function on the project, design, architecture, front-end, back-end, QA, deployment, and project management, has a clear owner, even if one person holds two hats early on.

- Every project gets a single source of truth for status, decisions, and trade-offs.
- Specialists prevent defects that generalists tend to miss, especially in testing, security, and infrastructure.
- Handoffs between phases stay clean because each role knows what to deliver and to whom.
- Capacity scales predictably, since you can add headcount inside a role rather than restructuring the whole team.

### What a modern web development team actually builds
The scope of a modern web development team extends well beyond static websites. The same web team structure delivers custom web applications, eCommerce platforms, customer and employee portals, progressive web apps (PWAs), CMS sites, and AI-powered features like chatbots, recommendation engines, predictive analytics, and generative interfaces embedded inside the product.

With the basic definition in place, the next question is which roles actually belong inside the team and what each one owns day to day.

Need a Pre-Built Web Development Team for Your Next AI-Powered Web App Launch?

Monocubed gives you a ready-to-ship cross-functional web team within one to four weeks so your launch stays on track without the typical multi-month hiring delay.

Schedule a Free Consultation

## Core Roles and Responsibilities Inside a Modern Web Development Team
A productive web development team is not a long list of titles. It is a small group where every role has a clear owner, a clear handoff, and a clear deliverable at each stage. The web team’s roles and responsibilities below cover almost every web project, though not every project needs all of them at the same time.

### 1. **Project manager**

The project manager owns scope, timeline, risk, and stakeholder communication across the build. They run sprints, track deliverables, and surface blockers before they become delays. Without this role, technical decisions happen in silos, and stakeholders lose confidence in delivery dates.

### 2. **Business analyst**

The business analyst translates business goals into clear, documented requirements. They run discovery interviews, map workflows, write user stories, and challenge assumptions before development starts. A strong BA prevents the most expensive bug in software: building the wrong thing correctly.

### 3. **Solution architect**

The solution architect designs the system’s technical foundation: tech stack, service boundaries, data flow, integrations, AI model placement, and scalability. They make early decisions that are expensive to reverse later. Getting this role right compounds value across the entire build.

### 4. **UI/UX designer**

The UI/UX designer turns research and requirements into wireframes, interactive prototypes, and a design system. They own information architecture, navigation, accessibility, and visual hierarchy that directly affect conversion. A weak design phase produces ambiguity that developers absorb as costly rework.

### 5. **Front-end developer**

The front-end developer transforms design mockups into responsive interfaces using HTML, CSS, JavaScript, and frameworks like React.js, Angular, or Vue.js. The roles of a web developer cover performance, accessibility, browser compatibility, and clean API integration with the back end. Our[ frontend web development company](https://www.monocubed.com/services/front-end-web-development-company/) supplies senior UI engineers on demand.

### 6. **Back-end developer**

The back-end developer builds server logic, databases, authentication, and APIs using Node.js, Python, Django, Laravel, Ruby on Rails, or .NET. They own data integrity, security, and integrations with ERP, CRM, payment, analytics, and AI services like OpenAI or Anthropic models.

### 7. **Full-stack developer**

The full-stack developer works across front-end and back-end and is most valuable on small teams, MVPs, and tight-deadline launches. On larger projects, full-stack engineers lead features end-to-end, bridge specialists, and keep velocity steady when one side is short on capacity.

### 8. **AI/ML engineer**

The AI/ML engineer designs and integrates intelligent features like chatbots, recommendation engines, predictive analytics, and generative interfaces. They select models such as GPT-4, Claude, or open-source LLMs, build retrieval layers, and own latency, cost, and accuracy trade-offs in live production.

### 9. **QA engineer**

The QA engineer designs and runs the test plan: functional, regression, cross-browser, accessibility, and load tests. They prevent defects from reaching production and own the release-readiness checklist. Cutting QA to save budget is the most common false economy in development.

### 10. **DevOps engineer**

The DevOps engineer sets up the CI/CD pipeline, manages cloud infrastructure on AWS, GCP, or Azure, automates deployments, and configures monitoring and alerting. Without a DevOps owner, releases become manual, error-prone events that slow down the delivery cadence over time.

### 11. **SEO specialist**

The SEO specialist makes the platform discoverable: technical SEO, structured data, sitemaps, Core Web Vitals, and on-page optimization. On a content-driven site or eCommerce platform, this role pays for itself within the first quarter through compounding organic traffic at scale.

A well-built team covers each of these functions, even if one person holds two hats. The next question is how to scale that role mix to the size of your project and the maturity of your product.

## Web Development Team Size by Project Stage: MVP, Growth, and Enterprise
Team size should scale with the maturity and complexity of the project, not the size of the company behind it. A four-person startup team and a 20-person enterprise team can both be the right answer; what matters is whether the website development team structure matches the work to be done. The table below maps team size to project stage and the roles most commonly active at each level, so you can benchmark your own setup against typical patterns.

| **Project Stage** | **Typical Team Size** | **Core Roles** | **Typical Timeline** |
|---|---|---|---|
| MVP or early-stage | 3–5 people | PM (part-time), UI/UX designer, full-stack developer (with AI exposure), QA (part-time) | 8–16 weeks |
| Growth-stage | 6–10 people | PM, BA, designer, 2 front-end devs, 2 back-end devs, AI/ML engineer, QA, DevOps | 4–9 months |
| Enterprise | 10+ people | PM, BA, architect, designers, multiple FE/BE devs, AI/ML engineer(s), QA, DevOps, SEO | 6–18 months |

Each stage corresponds to a different question the team is built to answer, and the role mix is what makes that answer reliable.

### MVP or early-stage team
An MVP team’s job is to validate a hypothesis with paying or active users as quickly as possible, without over-investing in infrastructure that may need to change. Three to five people are typical: a designer, one or two full-stack developers (ideally with API-level AI integration experience), and a part-time PM and QA.

The team is cross-functional, owns the full stack, and trades specialization for speed. Decisions are made fast, and the same engineers who build a feature often deploy and monitor it. The risk at this stage is over-hiring before product-market fit is proven, which locks you into a cost base your runway can’t support.

### Growth-stage team
Once a product has traction, the question shifts from validation to scale, and the team structure has to follow. The team adds dedicated front-end and back-end developers, a business analyst, an AI/ML engineer, full-time QA, and a DevOps engineer to handle infrastructure and release frequency. Most growth-stage builds at this point are full custom web applications rather than templated sites.

Partnering with experienced[ web application development services](https://www.monocubed.com/services/web-app-development/) gives buyers immediate access to a six- to ten-person squad working in two-week sprints, with a clear backlog, a release calendar, and weekly stakeholder reviews. Sprint velocity becomes a metric the team tracks, and roadmap decisions are made with data rather than intuition.

### Enterprise team
Enterprise projects involve compliance, multiple integrations, large user bases, and AI-powered features at scale. The web development team structure grows to include a solution architect, multiple designers, dedicated SEO and accessibility specialists, AI/ML engineers, and several coordinated sub-squads under one program manager. Governance becomes formal, which is why an enterprise-grade delivery partner usually beats a generalist agency at this scale.

Sizing the team correctly is one decision. Knowing when each role is active across the lifecycle is another aspect, which is where the development process comes in.

Stop Staffing Every Role From Day One. Build a Phase-Aware Team Instead.

Monocubed maps web development roles to project phases so you pay for specialists only when they are actively building, which keeps your monthly burn predictable.

Book a Strategy Call

## How Each Web Development Role Maps to the Six-Phase Delivery Process
A web development team is most efficient when each role is active during the phases that actually need it. Many projects waste capacity by staffing every role from day one, then losing momentum when key specialists are idle for weeks. Mapping roles to phases gives you a realistic resourcing plan instead of a static org chart, and it surfaces the moments when you need to bring in or rotate out specific specialists.

The six phases below cover the lifecycle most teams follow, and our deep dive on the[ website development process](https://www.monocubed.com/blog/website-development-process/) breaks down the timeline, deliverables, and common pitfalls inside each stage if you want a fuller picture before mapping your own roles.

### 1. **Discovery and requirements**

The PM, BA, and solution architect run this phase end-to-end. They interview stakeholders, document requirements, define scope, and produce the technical brief that the rest of the team will build from. Rushing discovery reliably produces late, over-budget projects.

### 2. **Design and architecture**

The UI/UX designer leads this phase, supported by the architect on data flow and integration boundaries. Front-end and back-end leads weigh in on technical feasibility. The output is a clickable prototype, design system, and architecture document that the developers build against.

### 3. **Development sprints**

Front-end, back-end, full-stack, and AI/ML developers do the bulk of the work, with the designer supporting refinements and the PM running sprint ceremonies. QA writes test cases in parallel. Most modern teams run two-week sprints using the Atlassian Agile framework.

### 4. Quality assurance and testing
QA leads this phase, with developers fixing what testing surfaces. Accessibility, performance, security, and cross-browser testing all happen here, alongside functional and regression suites. DevOps prepares staging environments, and the team runs at least one full dry run before release.

### 5. **Deployment and launch**

DevOps owns the release itself. The PM coordinates the launch sequence across stakeholders, developers stand by for hot fixes, and QA runs smoke tests once the new build goes fully live. The SEO specialist verifies indexing, redirects, and structured data.

### 6. **Maintenance and scaling**

Post-launch, the team usually scales down to match steady-state demand. A smaller crew of developers, a part-time DevOps engineer, and QA handle bug fixes, performance tuning, and feature requests. The architect re-engages for any major change in scale or direction.

Mapping roles to phases makes resourcing predictable. The next decision is whether to staff those roles internally or through an external partner.

## In-House vs Outsourced Web Development Team: Trade-Offs, Costs, and Best Fit
The most expensive hiring decision in web development is structural, not individual. Choosing between an in-house team, an outsourced partner, and a hybrid model determines your cost base, your speed, and how much project-management overhead you carry across the build. The table below compares the three factors that matter most when buyers actually sit down to decide.

| **Factor** | **In‑House** | **Outsourced** | **Hybrid** |
|---|---|---|---|
| Cost predictability | Fixed (high) | Variable (lower) | Mixed |
| Speed to start | 2–4 months | 1–4 weeks | 2–6 weeks |
| Access to specialists | Limited | Broad | Broad |
| Day‑to‑day control | Highest | Contract-based | Shared |
| Scalability up or down | Slow | Fast | Fast |
| Best for | Long‑term core product | Defined-scope builds, augmentation | Mature products with peak demand |

Each model fits a specific situation, so the answer for one company isn’t automatically the right answer for another.

### When an in-house team makes sense
An in-house team is the right choice in specific situations:

- **The web platform is the core product** that you expect to evolve for years
- **You need tight day-to-day control** and fast feedback loops on every release
- **Deep institutional knowledge** that compounds across releases is critical
- **You can absorb fixed costs** even when capacity is partially underused

The trade-off is cost. Fully loaded developer costs (salary, benefits, taxes, equipment, overhead) usually run well above base pay, and you carry that cost whether the team is fully utilized or not. For pre-product-market-fit startups, the burn rate of a five-person team is often the difference between two more quarters of runway and an emergency raise.

### When outsourcing or a dedicated team makes sense
Outsourcing is the right call in several common scenarios:

- **Defined-scope builds** that need a clear contract, timeline, and deliverables
- **MVPs** where speed to first paying users matters more than long-term ownership
- **Time-bound projects** with fixed start and end dates
- **Team augmentation** during peak demand when in-house capacity falls short

A web agency team also delivers concrete advantages over hiring in-house:

- **Variable cost instead of fixed:** you pay for capacity only when it is actively building
- **Faster access to specialists:** AI/ML, DevOps, and security expertise without the recruiting cycle
- **No multi-month hiring delay:** the team starts in one to four weeks instead of months
- **Risk sharing:** delivery accountability sits with the partner, not your internal team

For buyers weighing the move, our full breakdown of the[ benefits of outsourcing web development](https://www.monocubed.com/blog/benefits-of-outsourcing-web-development/) covers the cost savings, talent access, faster time-to-market, and risk-sharing advantages that consistently show up in real engagements.

The trade-off is that you need a partner with a documented process and clear communication, or you give up the control benefit without saving the cost. Vetting the partner’s delivery process, not just their portfolio, is the highest-leverage step a buyer can take.

### Hybrid models and staff augmentation
Hybrid models combine in-house ownership with targeted outsourcing of specific functions:

- **External QA pod** to run testing while engineering ships features
- **Remote DevOps engineer** for CI/CD, infrastructure, and monitoring
- **Dedicated front-end squad** during a redesign or major feature push
- **Specialist consultants** for security, accessibility, or AI engineering

Hybrid models work when ownership and decision authority are clearly defined for each part of the build, with no ambiguity about who decides what. Engaging an experienced consulting partner early helps define those boundaries before you commit to a structure, which avoids the common pattern of a hybrid model that drifts into duplicated work.

Once you have decided how to source the team, the next question is the engagement model that controls how you actually pay for them.

## Engagement Models for a Web Development Team: Hourly, Part-Time, and Full-Time Compared
The engagement model defines how you pay for the team and how flexible the relationship is. Three options cover almost every web project. For full pricing details across hourly, retainer, and fixed-bid options, see our guide on[ website development cost](https://www.monocubed.com/blog/website-development-cost/).

### Hourly engagement
Hourly engagement fits small projects, short-term fixes, and specialist work like security reviews or accessibility audits. Industry rates typically range from $25–$49 per hour offshore to $100–$200+ per hour for senior US-based talent on Clutch and Upwork. Ideal for genuinely small or uncertain scope with no minimum commitment.

### Part-time dedicated developers (~80–100 hours per month)
A part-time dedicated developer typically commits 80–100 hours per month, around four to five hours per day. Industry rates run roughly $4,000–$15,000 monthly, depending on location and seniority. Suit ongoing maintenance, steady feature releases, or a second engineer where one full-time hire would be too much.

### Full-time dedicated developers (~160–176 hours per month)
A full-time dedicated developer commits 160–176 hours per month, working exclusively on your project. Industry cost ranges from $5,000–$15,000 monthly offshore to $10,000–$25,000+ monthly for nearshore or US-based developers. Closest outsourced model to having an in-house engineer, ideal for active builds and growth-stage products.

Choosing the model is the easy part. Hiring the right people inside that model is where most teams stumble, which is the focus of the next section.

Don’t Let Vague Engagement Models Drain Your Web Project Budget Across Sprints

Choose an engagement model that matches your demand, whether hourly for short bursts, 80 hours monthly for steady work, or 160 hours for active builds.

Discuss Your Project Now

## How to Hire a Web Development Team That Ships on Time and on Budget
Hiring a web development team is more about role coverage than finding talented individuals. Below are seven filters that separate teams that ship from teams that stall. For single specialist hires, see our guide on[ how to hire backend developers](https://www.monocubed.com/blog/how-to-hire-backend-developers/). It walks through the interview questions, take-home tests, and technical signals that separate strong server-side engineers from the rest.

### 1. **Define scope and outcomes before you hire**

A clear one-to-two-page brief covering goals, users, must-have features, and constraints is the best filter for candidates and partners. Without it, conversations drift toward what the developer wants to build instead of business needs. An ambiguous brief produces worst-case-priced proposals.

### 2. **Prioritize role coverage over role count**

A five-person team with a PM, a designer, two developers, and a QA engineer will outperform a seven-person team of all developers almost every time. When evaluating proposals, line up each role against the core functions and confirm a clear owner for each.

### 3. **Match domain experience to your industry**

A team that has built three healthcare portals understands HIPAA from day one. A team shipping multiple eCommerce platforms knows payment gateways and fraud rules. Industry and AI experience are two of the highest-leverage hiring filters available to most buyers.

### 4. **Test communication early**

Run a discovery call before any contract and treat it as a working session, not a sales pitch. If the team listens, asks sharp questions, and pushes back on assumptions, communication will be strong. The pattern shows in 30 minutes.

### 5. **Insist on a documented delivery process**

Ask the partner or in-house lead to walk through their development lifecycle: how they run sprints, when QA gets involved, how releases happen, and what weekly reporting looks like. A vague answer is a leading indicator of vague execution later.

### 6. **Plan for QA and DevOps from day one**

Teams that miss deadlines almost always cut these roles at the start and add them under pressure halfway through. Build them in from the first sprint instead, even as a part-time QA engineer and fractional DevOps owner. Both are non-negotiable.

### 7. **Confirm post-launch ownership**

Find out who owns the platform after go-live, who handles bug fixes and feature requests, and what the support agreement covers. The first 90 days surface issues real users find, but staging is missed, so coverage in that window is critical.

A team built against these principles tends to ship on time, hold its quality bar, and scale with your business as your roadmap grows. The next step is putting that team into action.

## Build Your AI-Powered Web Development Team With Monocubed
The right web development team is less about headcount and more about whether the structure covers every function your project actually needs. Composition beats size, especially in the first six months when architecture, design, and delivery decisions get locked in.

With 6+ years of web delivery experience, 200+ shipped projects, and a team of 50+ developers spanning front-end, back-end, full-stack, UI/UX, QA, DevOps, and AI/ML engineering, Monocubed assembles dedicated teams that scale cleanly from MVP squads to full enterprise programs.

As an AI-focused web development partner, we build chatbots, recommendation engines, predictive analytics, and generative interfaces into client platforms using GPT-4, Claude, and self-hosted LLMs, all backed by 98% client satisfaction, a 99.9% uptime guarantee, and ISO 9001-certified delivery.

Ready to assemble a web development team for your next AI-powered build? Schedule a free 30-minute consultation with Monocubed to walk through your scope, ideal team composition, engagement model, and cost breakdown, and move from planning to building with confidence.

Before you book that call, the most common questions buyers ask about web development team setup are answered below.

## Frequently Asked Questions

1.

### How many people should be on a web development team?

     Most web projects run with three to ten people. An MVP needs three to five (a designer, one or two developers, plus a part-time PM and QA). A growth-stage product runs six to ten with dedicated front-end, back-end, QA, and DevOps roles. Enterprise builds need ten or more, organized into smaller squads under one program manager. Size scales with project stage.
2.

### What is the difference between a web development team and a software development team?

     A web development team specializes in browser-based products: websites, web applications, eCommerce platforms, portals, and PWAs. A software development team is broader and covers desktop applications, mobile apps, embedded systems, and back-end services that may have no user-facing front end at all. The skill overlap is significant, but a web team specifically prioritizes browser rendering, responsive design, and web-stack frameworks.
3.

### How much does it cost to hire a web development team?

     Cost depends on team size, location, and engagement model. A US-based in-house team of five can run into six figures per month once salaries, benefits, and overhead are loaded. An outsourced dedicated team of five to seven typically falls between $20,000 and $40,000 per month. Hourly rates on Clutch for web development companies average $25 to $49 per hour for standard roles.
4.

### Can a single full-stack developer replace a whole team?

     Only on the smallest projects. A single full-stack developer can ship an MVP or a brochure site solo, but full coverage of design, testing, deployment, AI integrations, and ongoing maintenance is more than one person can reliably sustain at quality. Most successful teams add a dedicated designer and a part-time QA engineer at the earliest stage and grow from there.
5.

### How long does it take to assemble a web development team?

     Assembling an in-house team usually takes two to four months once you account for sourcing, interviews, offers, equipment setup, and onboarding. Outsourced or dedicated teams can start in one to four weeks, depending on role mix and current availability with the provider. Hybrid models fall between the two, with shared roles available sooner than fully owned hires you fully control.
6.

### Which roles can be combined on a small web development team?

     On a small team, the PM and BA roles often combine, especially when one person can both write detailed requirements and run agile sprints. A full-stack developer can cover early DevOps work using managed services, and a designer with code experience can handle light front-end implementation. Avoid combining QA with a developer role, since self-testing misses what fresh eyes catch.
7.

### What does an AI/ML engineer do on a web development team?

     An AI/ML engineer designs and integrates the intelligent features inside the web platform, including chatbots, recommendation engines, predictive analytics, document understanding, semantic search, and generative interfaces. They select the right model (GPT-4, Claude, open-source LLMs, or fine-tuned in-house options), build retrieval and prompt-orchestration layers, and own all the production trade-offs around latency, accuracy, and ongoing model inference costs at scale.
8.

### How do you scale a web development team without disrupting active sprints?

     Scaling mid-sprint usually fails because new hires lose context fast. The proven approach is to ring-fence current sprints, onboard new members through pairing with existing engineers on shadow tasks, and fold them into delivery in the next sprint cycle. Use the existing PM to manage ramp-up, expand the backlog before adding capacity, and document conventions to absorb new hires smoothly.
9.

### What engagement models does Monocubed offer for web development teams?

     Monocubed offers three engagement models. Hourly covers small projects and one-off features with no minimum commitment. Part-time dedicated developers commit 80 hours per month, ideal for ongoing maintenance and steady feature work. Full-time dedicated developers commit 160 hours per month, working exclusively on your project, which fits active growth-stage builds. Each model includes transparent reporting and a clear scope agreement.
10.

### Does Monocubed build AI features into web platforms?

     Yes. Monocubed’s web development teams include dedicated AI/ML engineers who build chatbots, recommendation engines, predictive analytics, document understanding, semantic search, and generative interfaces directly into client web platforms. We work with GPT-4, Claude, open-source LLMs, and custom-trained models, and we own production trade-offs around latency, cost, and accuracy. AI features ship through the same sprint cadence as the rest of the build.


---

_View the original post at: [https://www.monocubed.com/blog/web-development-team/](https://www.monocubed.com/blog/web-development-team/)_  
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.5.3_  
_Generated: 2026-05-13 11:27:56 UTC_