Command Center Architecture
The Command Center is organized around a large pool of isolated profiles that can be assigned to geographic folders, market campaigns, and device types. The operating principle is simple: organize first, run small controlled batches, record observations, and adjust by market instead of applying one fixed setting everywhere.
Current Profile Inventory Working Baseline
MostLogin, DuoPlus & Environment Mix
Both platforms can serve as the profile-management layer. The workflow changes slightly depending on which platform is used, but the organizing principles stay consistent.
Platform Roles
| Platform | Best Fit | Operational Note |
|---|---|---|
| MostLogin | Fast profile loading and large profile management | Useful when managing large grouped profile inventories. Advanced automation can later be layered in through MCP + an LLM. |
| DuoPlus | Mobile-oriented cloud profiles | Built-in AI can simplify automation-oriented workflows. The environment is primarily mobile, so factor that into device mix planning. |
Proxy Selection Principle
There is no single proxy provider that fits every campaign. Select providers based on geography, cost, availability, session requirements, and your own operating needs. The provider notes shared in the Telegram group should be treated as guidance for choosing the best fit for a specific situation.
- Residential capacity: Can usually be operated at a higher rate because costs are typically easier to control.
- Mobile capacity: Use strategically because mobile proxy pricing can become expensive at scale.
- Mixed environment: Maintain a broad device/network mix instead of forcing every campaign into one connection type.
- Cost discipline: Build the profile pool around what the campaign actually needs rather than around one preferred vendor.
Geo Grouping & Campaign Folder Structure
Geographic organization is the key to keeping a large profile inventory manageable. Profiles should be labeled and grouped so operators can quickly identify which profiles belong to which market.
Profile Grouping Workflow
- Load the proxy inventory into MostLogin or your selected management environment.
- Mark profiles into groups using the grouping method demonstrated in the previous MostLogin training video.
- Group by geography so each city or target region has a clean pool of available profiles.
- Mix desktop and mobile profiles inside MostLogin geo groups rather than separating every device type into unrelated silos.
- Remember DuoPlus is primarily mobile when deciding how much mobile coverage already exists in a market.
- Place campaigns into geo folders so the same geographic pool can be used to test multiple brands in that market.
Google Search & Google Maps Session Workflow
Campaign sessions should follow a repeatable sequence while varying the actions naturally according to what is relevant for the business and the purpose of the test.
Session Sequence
Open the Assigned Geo Profile
Launch a profile from the market folder that matches the campaign being reviewed.
Choose Google Search or Google Maps
Sessions can alternate by day between standard Google Search and Google Maps so campaign observations are not limited to one surface.
Search the Target Keyword
Use the campaign keyword and review where the brand appears in the results for that environment.
Open the Brand Profile
Navigate to the intended brand result and review the listing experience from the selected profile.
Complete Relevant Listing Actions
Depending on the business, review listing content, read reviews, open the website, inspect directions where appropriate, or test the call action.
Staggered Batches & Market-Based Testing
Campaign volume should be selected from the competitive conditions of the market, not from a universal number. Smaller batches are easier to observe and adjust.
Scheduling Strategy
Profiles can technically be run together, but the preferred workflow is to stagger sessions throughout the day. Run a few profiles at a time across multiple batches rather than making every profile active in one block.
Competition-Based Volume Framework
| Market Type | Observed Working Range | Operating Guidance |
|---|---|---|
| Lower Competition | 2–5 sessions / interactions per day | Often the preferred steady testing range. Start small and observe. |
| Mid Competition | 5–10 per day | Increase only when the market warrants additional coverage. |
| Highly Competitive | Up to ~20 per day | Reserved for larger markets or more aggressive controlled testing. |
Track Observations, Then Adjust
Every campaign is different. The point of the Command Center is not to copy one number everywhere; it is to run controlled tests, watch the market response, and adjust based on competition and real campaign observations.
What to Record
- Date and market — Record where the campaign was active.
- Platform — Note whether the batch ran through MostLogin or DuoPlus.
- Device mix — Track how many mobile versus desktop profiles were used.
- Search surface — Record Google Search, Google Maps, or both.
- Session count — Track the total number of campaign sessions for the day.
- Observed position — Capture the before/after map or search position you are monitoring.
- Notes — Record anomalies, strong moves, flat performance, or anything that should change tomorrow's plan.
Aggressive Test Case: Locksmith
