Talk:Hypergiant Industries

Edit Request
NOTE: I am proposing this edit for FleishmanHillard on behalf of Hypergiant. I am a paid editor and am aware of the COI guidelines. I am submitting this edit request to propose revisions and additions to the article that reflect new information and better sourcing in hopes of making the article more current and up-to-date. I have outlined the proposed edits below by section, with the recommended edits below the outline. I also included all new sources within the proposed copy. Thank you for your consideration.

Infobox: Update the number of employees to 185 from 175.

Upfront/Summary Paragraph: ''Revise the opening paragraph to speak more specifically to what the company does and remove information about the founding of the company that should be in the infobox and history sections. Recommended update below.''

Hypergiant is an American technology company that offers artificial intelligence products and consulting services

History: ''Consolidate History, Acquisitions and Divisions sections into one section called History. Improve detail and sourcing for company divisions, investors and acquisitions. Recommended update below.''

Hypergiant was founded in February 2018 by Ben Lamm. It received funding from Align Capital, Mythic Ventures, Tony Robbins and Berringer Capital. The company provides commercial artificial intelligence products through its Space Age Solutions division, while Hypergiant Ventures funds investments in other AI technologies and companies.

In November 2018, Hypergiant launched Hypergiant Sensory Sciences, a division focused on the application of artificial intelligence to sensory data captured through cameras. Hypergiant’s Space Age Solutions division acquired Black Pixel, a Seattle-based app development company, in December 2018 for an undisclosed amount.

In February 2019, the company launched its Hypergiant Galactic Systems division which incorporates artificial intelligence into aerospace and astronautic hardware and software.

Hypergiant received additional funding from Sumitomo Corporation and Perot Jain. Align Capital; Tom Meredith, former CFO of Dell; and Austin, Texas mayor Steve Adler also provided funding.

In 2019, Hypergiant acquired Satellite & Extraterrestrial Operations & Procedures, a Houston-based satellite deployment company. Advisory Board: ''Add a notable source (TechCrunch) speaking to Bill Nye’s role on the Board. Recommended update below.''


 * William Sanford Nye
 * General (ret.) Lance W. Lord, USAF
 * Sangeeta Mudnal
 * John McKinley
 * Andrew Essex
 * Nova Spivack
 * Lisa Harris
 * Andrew Allen
 * Lloyd Walker
 * James D. Royston
 * Tom Meredith
 * Andy Hickl

Thank you for your consideration! Justin Goldsborough (talk) 03:14, 28 September 2019 (UTC)

Reply 27-SEP-2019
Spintendo 05:01, 28 September 2019 (UTC)

Edit Request
NOTE: I am proposing a second edit for FleishmanHillard on behalf of Hypergiant. I am a paid editor and am aware of the COI guidelines. I am submitting this edit request to propose four additional revisions and additions to the article that reflect new information in hopes of making the article more current and up-to-date. I have outlined the proposed edits below by section, with the recommended edits below the outline. I also included all new sources within the proposed copy.

Infobox: Please change the word "locations" to "employees." Hypergiant has 185 employees, not 185 locations.

History: Add two additional points and supporting sources to this section:
 * Add second sentence after footnote 9 with supporting source
 * Add citation needed and additional copy to fourth paragraph in History section

In November 2018, Hypergiant launched Hypergiant Sensory Sciences, a division focused on the application of artificial intelligence to sensory data captured through cameras. [9] Hypergiant’s Space Age Solutions division acquired Black Pixel, a Seattle-based app development company, in December 2018 for an undisclosed amount.

In February 2019, the company launched its Hypergiant Galactic Systems division which incorporates artificial intelligence into aerospace and astronautic hardware and software for the space industry.

Undisclosed paid warning box: Would you consider removing this warning box now that the article has been reviewed and updated via a proper edit request?

Appreciate your consideration! Justin Goldsborough (talk) 22:37, 30 September 2019 (UTC)

Reply 01-OCT-2019

 * 1) ✅ The references and claim were added.
 * 2) ❌ The maintenance template was not removed. It is recommended that, as a courtesy, you first try asking the editor who assigned the template — in this case  — in order to find out from them if it can be removed. Since they placed the template, they are in the best position to know whether or not the issues which caused its placement have been corrected. You may contact them directly by placing a new message on their talk page. In the unlikely event that you do not hear back from them after a reasonable amount of time, please reopen this request by altering the  template's answer parameter to read from yes to no.
 * The COI editor is reminded to please place all new talk page posts at the bottom of the talk page. Thank you! Regards, Spintendo  21:16, 1 October 2019 (UTC)

Maintenance Template
Would you consider removing the maintenance template placed on this article in July now that multiple COI edit requests have been submitted following Wikipedia guidelines and reviewed by COI editor ? Thank you for considering. Justin Goldsborough (talk) 12:49, 25 October 2019 (UTC)

Edit Request
NOTE: I am proposing an edit for FleishmanHillard on behalf of Hypergiant. I am a paid editor and am aware of the COI guidelines. I am submitting this edit request because a couple of edits marked approved in previous edit requests were not updated in the article. Could you please review at your convenience?

Infobox: Please change the word "locations" to "employees." Hypergiant has 185 employees, not 185 locations.

History: ''Update source where article currently says citation needed. Recommended update below.''

In 2019, Hypergiant acquired Satellite & Extraterrestrial Operations & Procedures, a Houston-based satellite deployment company

Thank you for considering this request. Justin Goldsborough (talk) 16:30, 28 October 2019 (UTC)

Reply 28-OCT-2019
Spintendo 01:48, 29 October 2019 (UTC)

RfC about maintenance template stating “Article may have been created or edited for undisclosed payments”
Should the maintenance template be removed from the article based on recent edits and clean up? Justin Goldsborough (talk) 23:31, 11 December 2019 (UTC)

DISCLOSURE: I proposed the original edit (removing the maintenance template) October 1 for FleishmanHillard on behalf of Hypergiant Industries. I am a paid editor for various brands and am aware of the COI guidelines.

Upon initial review of the Hypergiant Industries article, I noticed two previous editors -- and  -- had been blocked from editing for advertising and promotion by. Both decisions to block appeared warranted based on edit history. The second block of took place July 26, 2019.

Two months later, on Sept. 28, I submitted the first of three edit requests as a paid editor following Wikipedia paid editor guidelines and did not make any edits directly to the Hypergiant Industries article. My second edit, requested Oct. 1, included a request to remove the maintenance template on the article since proper editing protocol had now been followed. The COI editor who approved all three of my edit requests,, suggested I contact the editor who posted the maintenance template, , to request the template be removed. I did so and you can see our conversation at MER-C's Talk page.

and I were unable to reach an agreement on removing the maintenance template, which is why I’m posting this RfC. The maintenance template currently posted says the article “may require cleanup to comply with Wikipedia’s content policies.” There is a guideline for  paid-contribution disclosure within those content policies. That guideline was followed in my edit requests and I believe the article has now been “cleaned up” and therefore, the maintenance template should be removed. Thank you for your review and consideration. Justin Goldsborough (talk) 23:31, 11 December 2019 (UTC)


 * Tentative support.  A review of the current content of the article reveals just a small handful of simple, straight forward statements adequately sourced by citations to sources which, while they may not represent super high caliber publications, are nevertheless more than adequate to meet our WP:RS standards. Unless somebody has a substantive reason to continue to include the template--which frankly is an odd one, and particularly stigmatizing to the article's content, and thus potentially the subject itself)--I'd say I'm satisfied the article, although little more than a stub, satisfies the same standards I'd expect and hope to see had it been written by a disinterested party. Whether the article would exist absent the interest party is another question, but one not relevant to resolving the RfC's inquiry.


 * MER-C is technically correct when they note that they are not required to assist an editorial request--though, as a matter of Wiki-professional courtesy, I would argue that if one places a maintenance template in an article, they should be open to removing it unless a clear affirmative argument can be supplied for it remaining even if circumstances have changed. Much as I share some of MER-C's misgivings about paid editing, it is clear that his reason for declining to assist in removing the tag was out of a blanket distrust of COI editing and skepticism of any content it produces.  However, as an RfC respondent, I am not afforded that latitude in avoiding the underlying question in the same way--at least not if I want to be of use to the process. And again, I see nothing untoward, prejudicial, celebratory or inconsistent with the provided sources.


 * If someone can point out statements which are inaccurate, inconsistent with WP:WEIGHT or otherwise problematic, I'm happy to reconsider, but at present the article, skimpy though it may be, seems free of bias. Barring evidence to the contrary, I can't see the argument for keeping the tag; otherwise if the standard is that any article that ever had a COI editor will need to have this tag in perpetuum would clearly be a problematic standard and something that would need to be discussed by the larger community. I can't for example, ever imagine this thing being allowed longterm on our Facebook article or other content similarly concerned with high-profile tech companies that we know have extensive histories of COI editing involvement.


 * Indeed, I question the tag's value even in articles which are presently heavily skewed as a consequence of COI editing: as maintenance tags are concerned I think the issues with an article are better described by discussing what is potentially problematic with the content itself, rather than just making some nebulous assertion about editors who were once involved with it, which type of accusation typically creates more acrimony rather than contributing to solving the underlying content issues. Regardless, if it is going to stay, then its advocates would need to supply a substantive argument for lives issues on the article; lacking such a rational for keeping it, removal seems the only option under policy and within common sense. Snow let's rap 22:37, 15 December 2019 (UTC)


 * On a side note as to the broader issues with paid-for or otherwise COI editing in general, this isn't really the space to resolve them, but I will note that the community's decision to adopt the current model of allowing the practice but within tight constraints is largely based in the predicate assumption that a whack-a-mole approach to undisclosed editing (accompanied by unending accusations in editorial disputes) is far less desirable than creating a framework of rules to constrain the worst impulses of COI editing while still allowing first parties to have their concerns and suggestions vetted in the process of their representation on this project. Do I still have a massive extra layer of doubt when considering an edit recommend by a COI editor? Sure, but that's exactly the way I think things should operate: extra skepticism, oversight,and hurdles, but not refusing on principle to work with such editors.


 * At least, that's the system we have in place now, and it helps Mr. Goldsborough's case that he seems to have been scrupulously civil throughout the process and even very organized in presenting requests in a clear and transparent fashion. I think he's followed our current guidelines as closely as could be expected (and we do expect a lot in this regard), up to and including availing himself of RfC as the correct process at this juncture (and yet also no jumping to it too soon). I'd happier with a project that had no COI editing, but that's just an unrealistic expectation in our contemporary world, and I'd rather deal with a dozen Justins than one socking, manipulative, gaslighting undisclosed COI editor. Sno<b style="color: #b2dffe;">w</b> <b style="color: #d4143a">let's rap</b> 22:46, 15 December 2019 (UTC)


 * It still seems to be that the article is in common grounds with the edits made by the paid source. The template should stay, but rather than the current template, maybe it should be replaced by a NPOV template instead? Cook907 (talk) 17:36, 16 December 2019 (UTC)

Edit Request 12-23-19
NOTE: I am proposing an edit for FleishmanHillard on behalf of Hypergiant. I am a paid editor and am aware of the COI guidelines. I am submitting this edit request to improve the article by 1) bringing the article up to date (six of the 10 sources in this request were published in the last two months), 2) providing new information about the company's products and partnerships and 3) dividing the content into sections so it’s easier to read. Thank you for considering this request.

Overall Article: Add three new sections between the History and Advisory Board sections: 1) Partnerships, 2) Products, 3) Awards.

Partnerships: Add this section after the conclusion of the History section.

Booz Allen Hamilton

Hypergiant and Booz Allen Hamilton formed a strategic partnership on Aug. 6, 2019, to co-develop products and solutions for government entities and enterprises. The companies have worked together in the past, and Hypergiant CEO Ben Lamm has partnered with Booz Allen in previous ventures.

Products: Add this section after the conclusion of the Partnerships section.

Disaster Mapping System

Modzy is an AI marketplace developed by Booz Allen Hamilton that allows for enterprises to safely plug different AI models into their existing infrastructures. Hypergiant developed a model for Modzy called the Disaster Mapping System, which uses satellite and drone imaging, paired with AI, to help first responders perform building damage assessments in real time and determine what areas are most in need of a response.

EOS Bioreactor

Hypergiant launched the Eos Bioreactor in September 2019 to enable carbon capture and fight climate change. The bioreactor is a three-by-three-by-seven feet cube that can fit within office buildings. It’s powered by artificial intelligence and takes advantage of algae’s ability to capture carbon dioxide through photosynthesis – it can pull as much carbon dioxide from the air as an acre of trees. The algae the bioreactor creates can be harvested and processed to produce fuel, oils, nutrient-rich high-protein food sources, fertilizers, plastics and cosmetics.

Awards: Add this section after the conclusion of the Products section.


 * 2019 Best in Biz Awards: Most Innovative Company of the Year
 * DotCom Magazine: Impact Company of 2019

Appreciate you considering this request! Justin Goldsborough (talk) 03:38, 24 December 2019 (UTC)

Reply 24-DEC-2019
Regards, Spintendo  19:16, 24 December 2019 (UTC)
 * None of the proposed references for these claims were published without the assistance of company press releases, which largely informed their contents. Press releases by proxy are press releases nonetheless — and in this case serve as advertisement for the company's products and alliances.